MariaDB ColumnStore 1.0.7 GA Release Notes

Release date: 23rd January 2017

MariaDB ColumnStore 1.0.7 is a GA release of MariaDB ColumnStore. This release of MariaDB ColumnStore provides improvements over the previous 1.0.6 GA release.

MariaDB ColumnStore 1.0.7 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-506 - The MariaDB server version has been upgraded to version 10.1.21 including key security fixes. See the Server Release Notes for further details.
  • MCOL-462 - The AMI Image now supports utilization of the IAM role to manage keys. Please see the installing-and-configuring-a-columnstore-system-using-the-amazon-ami article for more details.
  • MCOL-481 - For a multi node install with mulitple UMs the installer now prompts you whether you want to install "MariaDB ColumnStore Schema Sync feature". If yes is answered then a default master / slave replication setup will be installed. Answer no if you prefer to perform your own setup or utilize another solution for this.

Bugs and issues fixed

  • MCOL-163 - DOUBLE PRECISION synonym for DOUBLE datatype not supported
  • MCOL-301 - aggregation over boolean expression fails with error 1178
  • MCOL-315 - switch to using os distribution version of libxml
  • MCOL-389 - cast of int mod function to char results in trailing decimal points
  • MCOL-449 - The generated server test DEB package doesn't install
  • MCOL-451 - findobjectfile should report filename for dictionary oid
  • MCOL-453 - change mcsadmin to only allow the module add/remove/disable commands from active PM Module
  • MCOL-454 - columnstore_info's total_usage() and table_usage() reported 0 usage on multi-node configuration
  • MCOL-455 - redistribute data's 'START REMOVE' option did not move data from the requested dbroot
  • MCOL-461 - remove the option of 'mp' in postConfigure
  • MCOL-462 - Amazon ColumnStore AMI support of IAM role with certificates
  • MCOL-467 - replication setup issues when adding modules in combined setup
  • MCOL-470 - merge server 10.1.20 code
  • MCOL-475 - Error in script /usr/local/mariadb/columnstore/bin/
  • MCOL-476 - postConfigure refers to 'Columnstore' instead of 'ColumnStore' as the product
  • MCOL-477 - can't reset autoincrement values
  • MCOL-481 - Add prompt to disable/enable mysql replication in postConfigure
  • MCOL-483 - Error in shell script
  • MCOL-488 - create AlarmConfig.installSave file
  • MCOL-493 - rpm install for multi node combined fails to setup logging on other nodes
  • MCOL-494 - Cannot execute query on mixed engine tables
  • MCOL-505 - Performance improvements to ExeMgr
  • MCOL-506 - merge server 10.1.21 release


Multi version upgrades are not supported, please upgrade versions prior to 1.0.6 before upgrading to 1.0.7:

Known issues and limitations

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

  • MCOL-73: Wide table formatted display causes frontend to return error
    • MariaDB ColumnStore supports wide tables storage
    • Displaying the query results on a large number of columns without formatting the column works
    • Displaying the query results on a large number of columns with formatting causes error at MariaDB Server level
  • MCOL-271 empty string values are treated as NULL. This means you cannot insert empty values into a NOT NULL string column.
  • MCOL-364: In a multi UM configuration where the default storage engine has been set to columnstore replicated tables are not created as columnstore tables. Avoid overriding the default storage engine and specify engine=columnstore on all table DDL.
  • 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-463 : gluster storage option in installer fails with an error. The installer option to install optimized for gluster storage will fail with an error. Manually set up gluster volumes can be used with the 'External' storage option.
  • 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.0.7 GA version.

  • The supported OS for the GA version are CentOS 6, CentOS 7, Debian 8.6, RedHat 6, RedHat 7, and Ubuntu 16.0.4.
  • Packages can be downloaded here
  • An Amazon AWS AMI Image is available for this release, please search for AMI name "MariaDB-ColumnStore-1.0.7". AMI specific installation instructions can be found here.
  • Instructions for setting up OS software repositories as the download mechanism will be published shortly.

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.