Release date: 9th February 2018
MariaDB ColumnStore 1.0.13 is a maintenance GA release of MariaDB ColumnStore. This release of MariaDB ColumnStore provides improvements over the previous 1.0.12 GA release.
MariaDB ColumnStore 1.0.13 is a GA release.
For an overview of MariaDB ColumnStore see
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 mariadb-columnstore@googlegroups.com
- The base MariaDB server version is now which include several maintenance and security fixes.
- MariaDB ColumnStore will automatically generate and save stack traces if a process crashes
- Add automatic stack trace to ColumnStore binaries
- multi-node install fails, mysqld didnt startup in time
- Merge
- ssh certificates aren't used in postConfigure nonDistributed installation with DataRedundancy between PMs enabled.
The following procedure outlines upgrading a 1.0.12 ColumnStore install to 1.0.13:
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).
There are a number bugs and known limitations within this version of MariaDB ColumnStore, the most serious of these are listed below.
: 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
RPM, Debian, and binary packages are provided for the Linux distributions supported by MariaDB ColumnStore 1.0.13 GA version.
The supported OS for the GA version are CentOS 6, CentOS 7, Debian 8.6, Debian 9.1, RedHat 6, RedHat 7, SUSE 12, and Ubuntu 16.0.4.
Packages can be downloaded
An Amazon AWS AMI Image is available for this release, please search for AMI name "MariaDB-ColumnStore-1.0.13". AMI specific installation instructions can be found .
Certified to run in Google Cloud Environment in the GA OSs.
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
Storage Engine -
MariaDB Server -
MCOL-1114 - Set cpack deb minimum version to 3.4
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.
MCOL-540 : In a non root Ubuntu install with local query enabled, the PM servers crash and restart on table creation.
The current logging default generates full verbose debug logs. This can be controlled by making logging configuration changes as described .
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 .
This page is: Copyright © 2025 MariaDB. All rights reserved.