MariaDB ColumnStore 1.1.4 GA Release Notes

You are viewing an old version of this article. View the current version here.

Release date: 20th April 2018

MariaDB ColumnStore 1.1.4 is a GA release of MariaDB ColumnStore. This is the fourth release of the MariaDB ColumnStore 1.1 series. This release of MariaDB ColumnStore provides improvements over the previous 1.1.3 GA release.

MariaDB ColumnStore 1.1.4 is a GA release.

For an overview of MariaDB ColumnStore see MariaDB ColumnStore Architectural Overview

Please provide feedback in JIRA for anything that is not working as expected so that we can fix it before we make the release available for the larger community. For general "how to questions" ask questions here or subscribe to

Notable changes

  • MCOL-1319 - The base MariaDB server version is now 10.2.14 which include several maintenance and security fixes.

Bugs and issues fixed

  • MCOL-912 - After adding two PMs, cpimport failed on newly added PMs
  • MCOL-1084 - table_usage() stored procedure show zero total usage when there are no dict columns
  • MCOL-1156 - Incorrect 0 row(s) affected on delete
  • MCOL-1182 - Cross-engine join query failing (single node)
  • MCOL-1196 - Error when using OR in case THEN portion
  • MCOL-1213 - SystemCatalog.getTable("table name") doesn't support uppercase letters
  • MCOL-1217 - newly added user module didnt have mysql replication slave setup
  • MCOL-1222 - ColumnStore start/restart can return before system is ready
  • MCOL-1228 - ALTER TABLE...CHANGE COLUMN broken for TEXT data types
  • MCOL-1230 - Change spark-connector's default compile option to ON
  • MCOL-1231 - Get a cmake error while building releases without both Python versions installed instead of a warning
  • MCOL-1233 - Ubuntu package has a bad dependency
  • MCOL-1234 - Nested CASE filters not processed
  • MCOL-1235 - procmgr crash - too many files open on alarm socket
  • MCOL-1241 - Move ColumnStore Kettle plugin to data-adapters git repository
  • MCOL-1245 - getting A fatal error in bulkinsert mariadb columnstore java api
  • MCOL-1246 - Trailing whitespace in CHAR/VARCHAR break string matches
  • MCOL-1252 - CSV load into columnstore table using Pentaho adapter with CS Bulk Import plugin doesn't succeed
  • MCOL-1255 - PDI CS Bulk Load plugin can't work with variable defined in file
  • MCOL-1262 - PDI CS naming conventions support
  • MCOL-1280 - MCSAPI C++ documentation, example incorrect
  • MCOL-1285 - Adapter can't recognize database schema with capital letters
  • MCOL-1298 - Bulk import of large CSV file causes restarting of the WriteEngineServer process on the PM
  • MCOL-1315 - Pentaho Bulk Load Module doesn't work
  • MCOL-1317 - Columnstore Cluster Tester tool does not check the availability of all ports needed to mcs operations
  • MCOL-1321 - bulk write sdk python bindings does not support status out param in setColumn
  • MCOL-1323 - cpimport Splitter has incorrect SIGPIPE mapping
  • MCOL-1331 - CASE1.DM.sql test fails
  • MCOL-1341 - test299 fails in select_case test
  • MCOL-1179 - Pentaho Data Integration / Kettle - Bulk API Java Binding
  • MCOL-1232 - Spark connector - support different ColumnStore configurations
  • MCOL-1258 - buildbot build the binary and rpm/deb tar.gz packages
  • MCOL-1283 - Try to pack/load the shared bulk write sdk library in/from jar to ease installation process
  • MCOL-1296 - Add debug output as an API option
  • MCOL-1312 - PDI version number - include git
  • MCOL-1318 - Columnstore Cluster Tester tool is evaluating Failure if Firewall Services or SELINUX are enabled
  • MCOL-1264 - List of manual tests performed
  • MCOL-1293 - new package dependency -
  • MCOL-1319 - Merge MariaDB 10.2.14
  • MCOL-1333 - Document that .tar.gz of RPM files is needed for addModule command

In addition, all bugs fixed in MariaDB ColumnStore 1.1.3 and earlier are implicitly included in this release.


The following procedure outlines upgrading a 1.1.3 ColumnStore install to 1.1.4:

Multi version upgrades generally will work using the same procedure however we can't test every possible permutation so you should test your specific scenario outside of production first if you wish to try this (and this is good practice regardless).

Known issues and limitations

There are a number bugs and known limitations within this version of MariaDB ColumnStore, the most serious of these are listed below.

  • MCOL-271 empty string values are treated as NULL. This means you cannot insert empty values into a NOT NULL string column.
  • MCOL-365: Log files created by load data infile remain in the bulk/data/log and /tmp directories. If storage is a concern these can safely be removed.
  • MCOL-540 : In a non root Ubuntu install with local query enabled, the PM servers crash and restart on table creation.
  • MCOL-624 :MariaDB 10.2 WF create MEDIAN, PERCENTILE_CONT and PERCENTILE_DISC Window functions. MariaDB ColumnStore 1.1 was rewritten to use the MariaDB 10.2 server parser code which does not support the percentile window functions. This will be added in a later release. A median function has been provided instead as part of the User Defined Aggregate Function framework that provides similar functionality or can be adapted to support percentiles other than 0.5.
  • MCOL-631 :Create table caused primproc crashed for a specific configuration
  • MCOL-643 :Implement ha_calpont_impl_rnd_pos. Sorting of long text columns may fail.
  • MCOL-695 :Implement joins between CHAR/VARCHAR and INT columns. ColumnStore now fails more consistently on incompatible join types. Explicit type casts must be used if this error is hit.
  • MCOL-713 : Some functions return "The maximum row size" error when TEXT/LONGTEXT is used in a table
  • MCOL-1224: post-install non-root has incorrect permissions for /etc/rc.local
  • MCOL-1225: LD_LIBRARY_PATH not set correctly in centos6 non-root install
  • The current logging default generates full verbose debug logs. This can be controlled by making logging configuration changes as described here.
  • While Millisecond and Microsecond storage is supported for datetime, time and timestamp columns, at this time the query results cannot return millisecond and microseconds.
  • UTF-8 Limitation
    • UTF-8 must be declared at the table level if the instance has been set up with a UTF-8 profile. Tables created with a non-matching character set will yield indeterminate results.
    • Viewing SQL output should be done using client software that supports UTF-8 character sets.
    • UTF-8 characters are not supported in object names.
  • Known security issues and fixes are documented here.


MariaDB ColumnStore Documentation


RPM, Debian, and binary packages are provided for the Linux distributions supported by MariaDB ColumnStore 1.1.4 GA version.

  • The supported OS for the GA version are CentOS 6, CentOS 7, Debian 8, Debian 9, RedHat 6, RedHat 7, SUSE 12, and Ubuntu 16.04.
  • Packages can be downloaded here or can be installed from the repositories.
  • An Amazon AWS AMI Image is available for this release, please search for AMI name "MariaDB-ColumnStore-1.1.4". AMI specific installation instructions can be found here.
  • Certified to run in Google Cloud Environment in the GA OSs.

Source code

The source code of MariaDB ColumnStore is tagged at GitHub with a tag, which is identical with the version of MariaDB ColumnStore. For instance, the tag of version X.Y.Z of MariaDB ColumnStore is columnstore-X.Y.Z. Further, master always refers to the latest released non-beta version.

The source code is available at these locations


Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.