Release notes for MariaDB ColumnStore 1.0
Release date: 14 June 2016
MariaDB ColumnStore 1.0.1 is the development version of MariaDB ColumnStore. It is built by porting InfiniDB 4.6.2 on MariaDB 10.1.14.
MariaDB ColumnStore 1.0.1 is an Alpha release.
Do not use alpha releases on production systems!
This is the first MariaDB ColumnStore release, and we are releasing it now to get it into the hands of any one who might want to test it. We plan to do several Alpha releases, each with increased stability and more features.
Note that this is an early Alpha release of MariaDB ColumnStore in MariaDB 10.1.14. The porting work from MySQL 5.1 is done, but not all features have been fully tested. This release is only meant for testing, not for using in production!
To understand what to expect from this release, a little background is needed: MariaDB ColumnStore is based on the MySQL 5.1 InfiniDB release, which was a stable product with a lot of happy users. To make this more modern and easier to develop, we moved the InfiniDB code to MariaDB 10.1.14 and renamed it ColumnStore. As most of the MariaDB ColumnStore code is unchanged and as MariaDB 10.1.14 code is stable, the possible problems are mostly in the interface between MariaDB Server and MariaDB ColumnStore.
We have not yet had time to ourselves to extensively test all MariaDB ColumnStore features, and MariaDB ColumnStore has not yet been tested by a larger community, so there may be some issues that need to be fixed in the next releases. We do, however, expect that most things should work and be reasonably stable.
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
Porting of InfiniDB source code as “columnstore” storage engine on MariaDB 10.1.14
All client applications using ODBC, JDBC, MySQL Clients, or MariaDB Clients can connect to and query MariaDB ColumnStore
Windowing Functions Supported: AVG, COUNT, CUME_DIST, DENSE_RANK, MAX, MEDIAN, MIN, NTILE, PERCENT_RANK, PERCENTILE_CONT, PERCENTILE_DISC, RANK, ROW_NUMBER, STDDEV, STDDEV_POP, STDDEV_SAMP, SUM, VARIANCE, VAR_POP, VAR_SAMP
Bulk Data Load—High-speed data loading utility cpimport
ACID transactions
MariaDB SQL Syntax compliance (with the exceptions noted in known limitations and issues)
Cross Engine joins
Built-in HA
Renaming of the engine to columnstore
Console command line utility is now called mcsadmin and an alias ma is created upon install for the same
SQL client utility alias is now called mcsmysql
Install directory is now under /usr/local/mariadb/columnstore
Log directory is now under /var/log/mariadb/columnstore
The numeric data type range values for MariaDB ColumnStore are different from that of other storage engines in MariaDB Server 10.1 as documented here
There are a number bugs and known limitations within this early Alpha version of MariaDB ColumnStore, the most serious of these are listed below. These are expected to be fixed way before the Beta release. There are some known security issues. They are listed here
MCOL-82: Subquery using IN with VIEW returns incorrect results. Queries selecting from view and using IN in where clause with a subquery on another view returns incorrect results.
MCOL-37: Following three window functions do not return correct value
FIRST_VALUE
LEAD
LAG
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-45 : CREATE PROCEDURE fails.
Do not use stored procedure with this Alpha versionMCOL-16: LOAD DATA INFILE into datetime columns, data got saturated.
Do not use LOAD DATA INFILE when importing data into datetime columns
Use cpimport to bulk load data into MariaDB Columnstore instead. cpimports works correctly for datetime columns as well.
INSERT INTO works for datetime columns
MCOL-49: Drop table does not work if the PM node runs out of space.
MCOL-58: Non-Root install does not work in this release
Use root access to install this Alpha version
MCOL-39: console command "getSystemConfig" returns error for some parameter names 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.
The building of the software needs a special build environment. We're working on making it available for everyone to build.
MariaDB ColumnStore Documentation include architecture, getting started, SQL Syntax guide, How to manage and How to load data into MariaDB ColumnStore.
Detailed Installation Guide will be available in next version of the MariaDB ColumnStore 1.0 series
RPM and binary packages are provided for the Linux distributions supported by MariaDB ColumnStore 1.0.1 Alpha version.
The supported OS for this Alpha version are CentOS 6 and CentOS 7.
Packages can be downloaded here
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 - Source code for engine specific processes on UM and PM node
This page is: Copyright © 2025 MariaDB. All rights reserved.
Release date: 28th July 2017
MariaDB ColumnStore 1.0.10 is a maintenance GA release of MariaDB ColumnStore. This release of MariaDB ColumnStore provides improvements over the previous 1.0.9 GA release.
MariaDB ColumnStore 1.0.10 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 mariadb-columnstore@googlegroups.com
MCOL-802 - MariaDB ColumnStore is now based on MariaDB Server 10.1.25.
MCOL-379 - system down and high memory alarm set after install
MCOL-472 - mysqld not shutdown by shutdownsystem commands, sometimes
MCOL-538 - Argument in alias circumvents /.my.cnf option file
MCOL-626 - addModule should not be alowed on single-server installs
MCOL-674 - Update a column with a subquery resulted NULLs in the target column
MCOL-699 - mcsadmin display issue for getModuleDisk
MCOL-711 - GROUP_CONCAT function got ColumnStore stuck in "Join or subselect exceeds memory limit" error
MCOL-715 - Amazon Install - error when setting up UM storage as 'io1' volume type
MCOL-719 - Unexpected results using LEAST or GREATEST on aggregate
MCOL-723 - MariabDB ColumnStore Cluster tester tool
MCOL-730 - cross engine join query select on decimal bad precision/scale
MCOL-732 - Merge Server 10.1.24
MCOL-734 - Error messages referenced an invalid OAM command unassignPmDbrootConfig
MCOL-736 - transaction gets autocommitted if non columnstore query executed
MCOL-773 - system not startup up via postConfigure/startsSystem - remote_command issue
MCOL-793 - ORDER BY NULL breaks subsequent query
MCOL-794 - query cache not work with all engine with columnstore
MCOL-802 - Merge MariaDB 10.1.25 into 1.0
MCOL-811 - Logs going to system journal in Ubuntu instead of log files
MCOL-814 - PrimProc could not open file for OID after a outage recover from pm2 PrimProc
MCOL-829 - Implement stored procedure INSERT...SELECT
MCOL-834 - PrimProc thread leak if ExeMgr dies
Multi version upgrades are not supported, please upgrade versions prior to 1.0.9 before upgrading to 1.0.10:
There are a number bugs and known limitations within this 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.10 GA version.
The supported OS for the GA version are CentOS 6, CentOS 7, Debian 8.6, RedHat 6, RedHat 7, SUSE 12, 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.10". AMI specific installation instructions can be found here.
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 - Source code for engine specific processes on UM and PM node
This page is: Copyright © 2025 MariaDB. All rights reserved.
Release date: 18th August 2017
MariaDB ColumnStore 1.0.11 is a maintenance GA release of MariaDB ColumnStore. This release of MariaDB ColumnStore provides improvements over the previous 1.0.10 GA release.
MariaDB ColumnStore 1.0.11 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 mariadb-columnstore@googlegroups.com
MCOL-792 - Debian 9 is now a supported platform.
MCOL-400 - On a 2PM combo stack with query stats enabled, one of the PMs returned an error when queries is executed
MCOL-515 - GROUP BY in a cross engine subquery generates bad results
MCOL-744 - primproc crashes sometimes in test001 regression test runs during drop table
MCOL-792 - support debian 9
MCOL-812 - Cross engine join and a filter where the string contains a quote character
MCOL-830 - CrossEngineSupport can not retrieve multi byte fields normally
MCOL-835 - Killing MariaDB connections can crash ExeMgr
MCOL-845 - postConfigure creates a list of dbroots and assigns them device nodes, it starts at 'g' and increments, but it skips 'k'. system fails to start
MCOL-849 - Process Manager leaving files called '+' lying around
MCOL-850 - ProcMgr crashes when too many 'getactivealarm' calls are made.
MCOL-857 - PrimProc thread leak on ByteStream advance
MCOL-860 - temp file error when using yum localinstall
MCOL-864 - Ubuntu columnstoreClusterTester.sh incorrectly raises issue for snappy package
MCOL-868 - merge mariadb server 10.1.26
Multi version upgrades are not supported, please upgrade versions prior to 1.0.10 before upgrading to 1.0.11:
There are a number bugs and known limitations within this 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.
MCOL-540 : In a non root Ubuntu install with local query enabled, the PM servers crash and restart on table creation.
MCOL-892 : 1.0.11 upgrade failed when base directory is nfs mounted
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.11 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 here
An Amazon AWS AMI Image is available for this release, please search for AMI name "MariaDB-ColumnStore-1.0.11". AMI specific installation instructions can be found here.
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 - Source code for engine specific processes on UM and PM node
This page is: Copyright © 2025 MariaDB. All rights reserved.
Release date: 14th December 2017
MariaDB ColumnStore 1.0.12 is a maintenance GA release of MariaDB ColumnStore. This release of MariaDB ColumnStore provides improvements over the previous 1.0.11 GA release.
MariaDB ColumnStore 1.0.12 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 mariadb-columnstore@googlegroups.com
MCOL-444 - split character import issue
MCOL-445 - configxml.sh should be case in-sensitive.
MCOL-446 - mycnf config change request
MCOL-662 - Unexpected results in cross engine join
MCOL-837 - postConfigure - WARNING: Mismatch between FilesPerColumnPartition check should be removed
MCOL-859 - Running TRUNCATE on many tables in parallel seems to eventually deadlock
MCOL-877 - Not all data escaped when inserting with select statement from innodb table into columnstore
MCOL-890 - group_contact returns garbage
MCOL-892 - 1.0.11 upgrade failed when base directory is nfs mounted
MCOL-895 - INSERT after ALTER TABLE can corrupt HWM
MCOL-898 - NULL operand ignored in vtable mode when querying view
MCOL-911 - exemgr crashes with a nested aggregate multiplication query
MCOL-936 - Binary installer fails due to expect skipping
MCOL-940 - merge server 10.1.28
MCOL-942 - Setting up of the Master/Slave Replication should not be done on start system
MCOL-943 - multi-node postConfigure fails when mysql password is set.
MCOL-944 - coalesce with count(distinct) can lead to incorrect results
MCOL-945 - MariaDBReplication slave messages is incorrectly sending updates to PM nodes
MCOL-954 - mysqld crashing on slave replication UMs
MCOL-973 - ArithmaticColumn parsing can cause crash
MCOL-976 - System in DBRM_READ_ONLY mode after Non-parent PM recovery under DataRedundancy
MCOL-979 - Crash with LEAD function in ColumnStore with 'char' field type
MCOL-985 - buildAggregateColumn needs to handle error code
MCOL-994 - cpimport failed with a "new extent FBO too high for current file error"
MCOL-1008 - LDI and INSERT...SELECT causes mysqld to crash with long VARCHAR entries
MCOL-1016 - information_schema.columnstore_extents data_size calculation incorrect
MCOL-1029 - Logic issue breaking multiple where conditions
MCOL-1032 - merge server 10.1.29
MCOL-1040 - ERROR 2013 (HY000): Lost connection to MySQL server during query
MCOL-1055 - cluster tester issues - backport from 1.1
MCOL-1068 - Compression ratio miscalculation when there are uncompressed columns
MCOL-1082 - row_count() function always returns 0 for any engine
MCOL-1095 - debian 9.2 cluster tester issues - fix libiao1
The following procedure outlines upgrading a 1.0.11 ColumnStore install to 1.0.12:
1.0.11 GA to 1.0.12 upgrade procedure 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.
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.
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 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.12 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 here
An Amazon AWS AMI Image is available for this release, please search for AMI name "MariaDB-ColumnStore-1.0.12". AMI specific installation instructions can be found here.
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 - Source code for engine specific processes on UM and PM node
This page is: Copyright © 2025 MariaDB. All rights reserved.
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 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 mariadb-columnstore@googlegroups.com
MCOL-1085 - MariaDB ColumnStore will automatically generate and save stack traces if a process crashes
MCOL-1085 - Add automatic stack trace to ColumnStore binaries
MCOL-1106 - multi-node install fails, mysqld didnt startup in time
MCOL-1206 - Merge MariaDB 10.1.31
MCOL-1086 - ssh certificates aren't used in postConfigure nonDistributed installation with DataRedundancy between PMs enabled.
MCOL-1114 - Set cpack deb minimum version to 3.4
The following procedure outlines upgrading a 1.0.12 ColumnStore install to 1.0.13:
1.0.12 GA to 1.0.13 upgrade procedure 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.
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.
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 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.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 here
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 here.
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 - Source code for engine specific processes on UM and PM node
This page is: Copyright © 2025 MariaDB. All rights reserved.
Release date: 29th May 2018
MariaDB ColumnStore 1.0.14 is a maintenance GA release of MariaDB ColumnStore. This release of MariaDB ColumnStore provides improvements over the previous 1.0.13 GA release.
MariaDB ColumnStore 1.0.14 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 mariadb-columnstore@googlegroups.com
MCOL-1434 - Merge MariaDB 10.1.33
The following procedure outlines upgrading a 1.0.13 ColumnStore install to 1.0.14:
1.0.13 GA to 1.0.14 upgrade procedure 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.
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.
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 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.14 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 here
An Amazon AWS AMI Image is available for this release, please search for AMI name "MariaDB-ColumnStore-1.0.14". AMI specific installation instructions can be found here.
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 - Source code for engine specific processes on UM and PM node
This page is: Copyright © 2025 MariaDB. All rights reserved.
Release date: 17th August 2018
MariaDB ColumnStore 1.0.15 is a maintenance GA release of MariaDB ColumnStore. This release of MariaDB ColumnStore provides improvements over the previous 1.0.14 GA release.
MariaDB ColumnStore 1.0.15 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 mariadb-columnstore@googlegroups.com
MCOL-1631 - Merge MariaDB 10.1.35
The following procedure outlines upgrading a 1.0.14 ColumnStore install to 1.0.15:
1.0.14 GA to 1.0.15 upgrade procedure 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.
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.
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 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.15 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 here
An Amazon AWS AMI Image is available for this release, please search for AMI name "MariaDB-ColumnStore-1.0.14". AMI specific installation instructions can be found here.
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 - Source code for engine specific processes on UM and PM node
This page is: Copyright © 2025 MariaDB. All rights reserved.
Release date: 13th February 2018
MariaDB ColumnStore 1.0.16 is a maintenance GA release of MariaDB ColumnStore. This release of MariaDB ColumnStore provides improvements over the previous 1.0.15 GA release.
MariaDB ColumnStore 1.0.16 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 mariadb-columnstore@googlegroups.com
MCOL-2136 - Use jemalloc as the main memory allocator. Please ensure jemalloc is installed on each ColumnStore node prior to installation or upgrade.
MCOL-1654 - Querystats table is broken
MCOL-2062 - cpimport scientific notation conversion problem
MCOL-2136 - Use jemalloc as the main memory allocator
MCOL-2149 - Regression in decimal saturation handling in cpimport
MCOL-2115 - Merge MariaDB 10.1.38 into server tree
MCOL-2120 - Check NUMA devel package is installed on BuildBot instances
The following procedure outlines upgrading a 1.0.15 ColumnStore install to 1.0.16:
1.0.15 GA to 1.0.16 upgrade procedure 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.
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.
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 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.16 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 here
An Amazon AWS AMI Image is available for this release, please search for AMI name "MariaDB-ColumnStore-1.0.16". AMI specific installation instructions can be found here.
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 - Source code for engine specific processes on UM and PM node
This page is: Copyright © 2025 MariaDB. All rights reserved.
Release date: 23 August 2016
MariaDB ColumnStore 1.0.2 is an alpha release of MariaDB ColumnStore. This is the second alpha release of MariaDB ColumnStore with improvements over previous alpha release of 1.0.1.
MariaDB ColumnStore 1.0.2 is an Alpha release.
Do not use alpha releases on production systems!
For an overview of MariaDB ColumnStore see MariaDB ColumnStore Architectural Overview
MariaDB ColumnStore 1.0.2 is an Alpha release. This is the second alpha release of MariaDB ColumnStore with improvements over previous alpha release of 1.0.1.
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
MCOL-70: systemd service support
MCOL-4 Build for CentOS 7
MCOL-5 Build for Ubuntu 16.04
MCOL-58 Non-root installs now works for columnstore mysql code
Below is list of some of the bugs and issues fixed. For the complete list please see here
MCOL-140: Concurrent Insert threads generate errors
MCOL-254: ColumnStore is limited to two columns in a GROUP BY statement
MCOL-67: config.log and possibly other autoconf artifacts are in source control
MCOL-69: autotools based build process does not work
MCOL-151: Columnstore engine not available after reboot
MCOL-39: console command "getSystemConfig" return API for some parameter names
MCOL-59: name change of Calpont.xml files
MCOL-71: Problem changing the MariaDB release version in Columnstore build
MCOL-113: install_calpont_mysql.sh returns function not found errors on a new installation
MCOL-138: postConfigure mentions MySQL
MCOL-139: MariaDB ColumnStore version confusion
MCOL-146: build enterprise rpms from new build processes
MCOL-68: Makefile.in missing in oamapps/mcsadmin/
MCOL-64: Internal error: CAL0009: Error in dropping table from systables
With the fixing of MCOL-59, the MariaDB Columnstore Platform Configuration file name has changed between 1.0.1 and 1.0.2. So if you have a 1.0.0 or 1.0.1 system and you want to upgrade to 1.0.2, you will need to do the following as part of the upgrade process. If you decide to reinstall 1.0.2 from scratch, this is isn’t required.
For details on how to execute the workaround please see upgrading-mariadb-columnstore-from-102-to-103
There are a number bugs and known limitations within this early Alpha version of MariaDB ColumnStore, the most serious of these are listed below. These are expected to be fixed way before the Beta release. There are some known security issues. They are listed here
MCOL-82: Subquery using IN with VIEW returns incorrect results. Queries selecting from view and using IN in where clause with a subquery on another view returns incorrect results.
MCOL-37: Following three window functions do not return correct value
FIRST_VALUE
LEAD
LAG
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-45 : CREATE PROCEDURE fails.
Do not use stored procedure with this Alpha versionMCOL-16: LOAD DATA INFILE into datetime columns, data got saturated.
Do not use LOAD DATA INFILE when importing data into datetime columns
Use cpimport to bulk load data into MariaDB Columnstore instead. cpimports works correctly for datetime columns as well.
INSERT INTO works for datetime columns
MCOL-49: Drop table does not work if the PM node runs out of space.
MCOL-259: After starting MariaDB ColumnStore Service, if queries start within few nano-seconds, queries fail with “At least one DBRoot required for that query is offline“ message
Wait for 1 minute after the service is started, before starting to send queries
MCOL-256: Queries that have inline comments will produce erroneous results
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.
MariaDB ColumnStore Documentation
RPM and binary packages are provided for the Linux distributions supported by MariaDB ColumnStore 1.0.2 Alpha version.
The supported OS for this Alpha version are CentOS 6, CentOS 7 and Ubuntu 16.0.4.
Packages can be downloaded here
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 - Source code for engine specific processes on UM and PM node
This page is: Copyright © 2025 MariaDB. All rights reserved.
Release date: 20 September 2016
MariaDB ColumnStore 1.0.3 is an alpha release of MariaDB ColumnStore. This is the third alpha release of MariaDB ColumnStore with improvements over previous alpha release of 1.0.2.
MariaDB ColumnStore 1.0.3 is an Alpha release.
Do not use alpha releases on production systems!
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 mariadb-columnstore@googlegroups.com
MCOL-112 The base MariaDB server version is now 10.1.17, including the security fix for CVE-2016-6662 (MySQL Remote Root Code Execution / Privilege Escalation 0 day).
MCOL-171: A date of 0000-00-00 is now supported and will not be turned into NULL. Previous NULL conversions will remain as NULL
MCOL-274: The minimum possible data (apart from ‘0000-00-00’) has changed from ‘1400-01-01’ to ‘1000-01-01’ which is more in-line with MariaDB’s documented date range
Below is list of some of the bugs and issues fixed. For the complete list please see here
MCOL-281: LDI using cpimport pads char column values with spaces
MCOL-274: DATETIME field doesn't match with MySQL standard
MCOL-264: DDL parser doesn't support space instead of equals in table options
MCOL-259: intermediate regression test failures - At least one DBRoot required for that query is offline.
MCOL-256: Queries that have inline comments will produce erroneous results
MCOL-240: DBT3 query 11 returned an internal error, ExeMgr aborted
MCOL-173: "INSERT INTO tableName SELECT 42,100" not working correctly
MCOL-171: 0000-00-00 dates are not supported and are munged to NULL with no warnings
MCOL-80: EXTRACT() function returned assertion error
MCOL-45: CREATE PROCEDURE fails
Multi version upgrades are not supported, please upgrade versions prior to 1.0.2 before upgrading to 1.0.3. Details on upgrading from version to 1.0.2 to 1.0.3 can be found here.
Upgrade from MariaDB ColumnStore Alpha versions 1.0.0 and 1.0.1 is not supported, please upgrade to version 1.0.2 prior to upgrading to 1.0.3.
There are a number bugs and known limitations within this early Alpha version of MariaDB ColumnStore, the most serious of these are listed below. These are expected to be fixed way before the Beta release. There are some known security issues. They are listed here
MCOL-82: Subquery using IN with VIEW returns incorrect results. Queries selecting from view and using IN in where clause with a subquery on another view returns incorrect results.
MCOL-37: Following three window functions do not return correct value
FIRST_VALUE
LEAD
LAG
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-290: DecomSvr status incorrectly reported as Initial rather than Active.
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.
MariaDB ColumnStore Documentation
RPM and binary packages are provided for the Linux distributions supported by MariaDB ColumnStore 1.0.3 Alpha version.
The supported OS for this Alpha version are CentOS 6, CentOS 7 and Ubuntu 16.0.4.
Packages can be downloaded here
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 - Source code for engine specific processes on UM and PM node
This page is: Copyright © 2025 MariaDB. All rights reserved.
Release date: 26th October 2016
MariaDB ColumnStore 1.0.4 is a beta release of MariaDB ColumnStore. This is the first beta release of MariaDB ColumnStore with improvements over the previous 1.0.3 alpha release.
MariaDB ColumnStore 1.0.4 is a Beta release.
Do not use beta releases on production systems!
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 mariadb-columnstore@googlegroups.com
MCOL-303 - A build related performance regression in the 1.0.2 release has been fixed restoring performance to be comparable with the prior Infinidb versions.
MCOL-251 - MariaDB ColumnStore no longer issues snmp traps. As a result of this 2 prompts are removed from the postConfigure script relating to this.
MCOL-325 - the WEEK and YEARWEEK functions are now consistent with the MariaDB server implementation.
MCOL-305 - The base MariaDB server version is now 10.1.18. As a result of this the perl-DBD-MySQL package may need to be installed using an OS appropriate tool prior to installation of MariaDB ColumnStore.
Below is list of some of the bugs and issues fixed. A number of regression test and build related fixes were made in addition. For the complete list please see here
MCOL-21 - Create table failed due to Error updating BRM block version buffer overflow error
MCOL-74 - Nth_value() windowing function does not exist error
MCOL-75 - Last_value() Windowing function returned an syntax error
MCOL-78 - ROUND() function returns incorrect value
MCOL-98 - Behavioral differences between MariaDB and ColumnStore for few functions
MCOL-99 - EXTRACT() function returns an exception when processing *MICROSECONDS
MCOL-115 - Auto rollback is not occur when update caused a version-buffer-full error (autocommit=1)
MCOL-176 - DIV operator crashes PrimProc
MCOL-251 - does columnstore need to issue snmp traps?
MCOL-285 - Columnstore is few times slower than InfiniDB for DBT3 query #1
MCOL-287 - CPImport performance slowdown by 27% or more from a1.0.1 to 1.0.2
MCOL-289 - test001 bug2954.sql fails
MCOL-290 - decomsrv app reporting incorrect state
MCOL-292 - CentOS 7 RPM's don't depend on Boost
MCOL-297 - CHARACTER_LENGTH(datetime) returns wrong length
MCOL-299 - CHARACTER_LENGTH(float/decimal) returns wrong length
MCOL-302 - rpm -U reports errors
MCOL-303 - Performance drop between 1.0.1 and 1.0.2
MCOL-305 - MariaDB Server 10.1.18 Merge
MCOL-308 - Add CMake and RPM build checks for net-snmp
MCOL-325 - WEEK() handling needs to match MySQL's
MCOL-326 - RAND() behaves differently with negative seeds
MCOL-328 - REVERSE() adds extra character
MCOL-329 - Functions casting date/datetime 0 to NULL
MCOL-330 - Datetime to int conversion returns strange values
MCOL-331 - INSERT() function misbehaves with our of range parameters
MCOL-332 - MONTHNAME() to int should equal 0
MCOL-333 - subtime() off by one second
MCOL-335 - Many Window Functions erroniously return 0
MCOL-341 - mts_insert_select producing bad results
MCOL-343 - ha_calpont_execplan assigns String::ptr() to std::string
MCOL-347 - NULLIF datetime compare with date fails
Multi version upgrades are not supported, please upgrade versions prior to 1.0.3 before upgrading to 1.0.4. Details on upgrading from version to 1.0.3 to 1.0.4 can be found here.
Upgrade from MariaDB ColumnStore Alpha versions 1.0.0 to 1.0.2 is not supported, please upgrade to version 1.0.3 prior to upgrading to 1.0.4.
There are a number bugs and known limitations within this beta version of MariaDB ColumnStore, the most serious of these are listed below. These are expected to be fixed before the GA release.
MCOL-37: Following three window functions do not return correct value
FIRST_VALUE
LEAD
LAG
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-129 Direct insert of column store reserved values, for example -128 for tinyint in STRICT_ALL_TABLES mode will result in no insert and no warning. Be aware of the range limits for datatypes and avoid using STRICT_ALL_TABLES mode.
MCOL-271 empty string values are treated as NULL. This means you cannot insert empty values into a NOT NULL string column.
MCOL-334: Subquery using IN with VIEW returns incorrect results. Queries selecting from view and using IN in where clause with a subquery on another view returns incorrect results. If this functionality is desired then run set infinidb_vtable_mode=0; before executing the query. This will have a reduced performance impact.
MCOL-350: Selects with a where clause of = '0000-00-00' do not match. Datetime is not affected.
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-372: Frequent socket timeout logging. This can be suppressed through configuring a syslog blacklist file and restart the syslog daemon, for example /etc/rsyslog.d/01-blocklist.conf contains:
:msg,contains,"CAL0071: InetStreamSocket::read: timeout during readToMagic: socket read error: Success; InetStreamSocket:" ~MCOL-404: Non root user install does not work. Install as root instead for this release.
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 are documented here.
MariaDB ColumnStore Documentation
RPM and binary packages are provided for the Linux distributions supported by MariaDB ColumnStore 1.0.4 beta version.
The supported OS for this Alpha version are CentOS 6, CentOS 7 and Ubuntu 16.0.4.
Packages can be downloaded here
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 - Source code for engine specific processes on UM and PM node
This page is: Copyright © 2025 MariaDB. All rights reserved.
Release date: 24th November 2016
MariaDB ColumnStore 1.0.5 is a Release Candidate release of MariaDB ColumnStore. This release of MariaDB ColumnStore provides improvements over the previous 1.0.4 beta release.
MariaDB ColumnStore 1.0.5 is a Release Candidate release.
Do not use Release Candidate releases on production systems!
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 mariadb-columnstore@googlegroups.com
MCOL-385 - 10.1.19 Merge : ColumnStore is now based off the MariaDB Server release 10.1.19.
MCOL-404 - non-root install fails on centos7 : Non root installs now work.
MCOL-309 - Support method to report on data set size : Information schema tables are created to support reporting on table and column sizes. This is an initial implementation with some further improvements planned for the GA release. See documentation for further details.
An install for Debian 8.6 is now available.
Below is list of some of the bugs and issues fixed. A number of regression test and build related fixes were made in addition. For the complete list please see here
MCOL-37 - Five windowing functions that are returning incorrect results
MCOL-61 - Create AMI for MariaDB ColumnStore
MCOL-91 - SQL Statement cause syntax error when vtable mode = 1
MCOL-121 - MySQL client reports "stage 2 - enabling keys" for every query against a CS table.
MCOL-129 - INSERTIONS are lost, no ERROR reported for out-of-range values in STRICT mode
MCOL-218 - DROP DATABASE on a database with all empty tables is not accepted
MCOL-260 - update two tables with a subquery fails
MCOL-263 - With suspendDatabaseWrite enabled, LDI return an incorrect msg
MCOL-273 - During restart, ProcessManager sometimes generates a warning
MCOL-278 - drop table if exists creates error if table doesn't exist and schema out of synch
MCOL-309 - Support method to report on data set size
MCOL-334 - Bad NULL match in view subquery
MCOL-350 - can't select date value of 0000-00-00
MCOL-352 - substr() on view returns NULL sometimes
MCOL-361 - table mode 0 and 2 has bad result
MCOL-370 - enableLog / disableLog don't work
MCOL-372 - dbrm-worker node continuing issues socket read error log
MCOL-385 - 10.1.19 Merge
MCOL-386 - postConfigure should show cause of write error.
MCOL-387 - releasenum gets messed up when not hard set
MCOL-398 - remove the restriction in postConfigure for UM memory at 16G
MCOL-404 - non-root install fails on centos7
Multi version upgrades are not supported, please upgrade versions prior to 1.0.4 before upgrading to 1.0.5. Details on upgrading from version to 1.0.4 to 1.0.5 can be found here.
Upgrade from MariaDB ColumnStore Alpha versions 1.0.0 to 1.0.2 is not supported, please upgrade to version 1.0.4 prior to upgrading to 1.0.5.
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-421: If a password was set for the root localhost user in the prior installed version then upgrade will fail. The workaround is to clear the password temporarily prior to the upgrade and reapply after the upgrade is complete.
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 and binary packages are provided for the Linux distributions supported by MariaDB ColumnStore 1.0.5 RC version.
The supported OS for this RC version are CentOS 6, CentOS 7, Debian 8.6, and Ubuntu 16.0.4.
Packages can be downloaded here
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—Source code for engine specific processes on UM and PM node
This page is: Copyright © 2025 MariaDB. All rights reserved.
Release date: 14th December 2016
MariaDB ColumnStore 1.0.6 is a GA release of MariaDB ColumnStore. This release of MariaDB ColumnStore provides improvements over the previous 1.0.5 RC release.
MariaDB ColumnStore 1.0.6 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 mariadb-columnstore@googlegroups.com
MCOL-272 - generate debian packages: A debian package build is now available for Debian and Ubuntu in addition to the binary install.
MCOL-307 - implement redistribution logic : An mcsadmin utility command is provided to support redistribution of partitions. For more details see the columnstore-redistribute-data article.
MCOL-311 - utility for finding objects file : An mcsadmin utility command is provided to support locating files by table or column. For more details run 'help findObjectFile' in the mcsadmin utility.
MCOL-406 - Stored procedures required for I_S tables : Convenience stored procedures are now provided for common tasks in querying the ColumnStore information schema tables. For more details see the columnstore-information-schema-tables article.
MCOL-272 - generate debian packages
MCOL-307 - implement redistribution logic
MCOL-311 - utility for finding objects file
MCOL-398 - remove the restriction in postConfigure for UM memory at 16G
MCOL-406 - Stored procedures required for I_S tables
MCOL-420 - Add alias for cpimport in columnstoreAlias
MCOL-421 - system upgrade install fails when a mysql root password is set
MCOL-422 - Amazon AMI single-server Columnstore didn't restart on a stop/start
MCOL-424 - cross engine subquery losing where clause causing incorrect results
MCOL-430 - invalid null date values for cross engine join query
MCOL-433 - Small row results can cause CrossEngine buffer underflow
MCOL-434 - DecomSvr fails to cleanly start when a Amazon Instance is stopped/started
MCOL-435 - Amazon AMi multi-node system didnt successfully restart after a stop/start
MCOL-441 - Segfault on query after an error
MCOL-442 - Default date value doesn't allow zero date
MCOL-457 - null bit header error when the number of NULL columns is divisible by 8 and the last column is a NOT NULL
Multi version upgrades are not supported, please upgrade versions prior to 1.0.4 before upgrading to 1.0.6:
Upgrade from MariaDB ColumnStore Alpha versions 1.0.0 to 1.0.2 is not supported, please upgrade to version 1.0.4 or 1.0.5 prior to upgrading to 1.0.6.
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-454 : columnstore_info's total_usage() and table_usage() reported 0 usage on multi-node configuration. The stored procedures and information_schema.columnstore_files return incorrect path and size information for a multi node install.
MCOL-463 : gluster storage option in installer fails withe 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.6 RC 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.6". AMI specific installation instructions can be found here.
Instructions for setting up OS software repositories as the download mechanism will be published shortly.
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 - Source code for engine specific processes on UM and PM node
This page is: Copyright © 2025 MariaDB. All rights reserved.
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 mariadb-columnstore@googlegroups.com
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.
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/rsync.sh
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:
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.
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 - Source code for engine specific processes on UM and PM node
This page is: Copyright © 2025 MariaDB. All rights reserved.
Release date: 26th March 2017
MariaDB ColumnStore 1.0.8 is a maintenance GA release of MariaDB ColumnStore. This release of MariaDB ColumnStore provides improvements over the previous 1.0.7 GA release.
MariaDB ColumnStore 1.0.8 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 mariadb-columnstore@googlegroups.com
MCOL-609 - ColumnStore has been updated to MariaDB server 10.1.22. This results in some os package dependency changes:
'snappy' library added.
MCOL-591 - The auth_gssapi plugin is now bundled with ColumnStore enabling kerberos based authentication. auth_gssapi plugin missing from columnstore package distribution
MCOL-592 - The auth_pam plugin is now bundled with ColumnStore enabling LDAP based authentication.
MCOL-611 - Bulk cpimport has been optimized to reduce execution overhead in determining completion across multiple nodes.
MCOL-640 - Support Google Cloud Environment
MCOL-533 - table_usage() has a calculation error
MCOL-547 - enforce limitation of postCfg needing to be run on pm1
MCOL-591 - auth_gssapi plugin missing from columnstore package distribution
MCOL-592 - auth_pam plugin missing from columnstore
MCOL-604 - mcsadmin startup changes permission on /dev/shm
MCOL-605 - Crash when running table_usage
MCOL-607 - post-install change /var/log/mariadb to 777 permissions, causing issues
MCOL-609 - merge server 10.1.22 release
MCOL-610 - warning error reported after upgrade to 1.0.6
MCOL-611 - with 6 PMs, cpimport has an long lag time
MCOL-616 - addmodule failure on ubuntu system after a 1-pm install is done
MCOL-617 - postConfigure/addModule for ubuntu/debian takes too long to perform
MCOL-618 - innodb query crash only happens on columnstore server
Multi version upgrades are not supported, please upgrade versions prior to 1.0.7 before upgrading to 1.0.8:
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.8 GA version.
The supported OS for the GA version are CentOS 6, CentOS 7, Debian 8.6, RedHat 6, RedHat 7, SUSE 12, 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.8". AMI specific installation instructions can be found here.
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 - Source code for engine specific processes on UM and PM node
This page is: Copyright © 2025 MariaDB. All rights reserved.
Release date: 11th May 2017
MariaDB ColumnStore 1.0.9 is a maintenance GA release of MariaDB ColumnStore. This release of MariaDB ColumnStore provides improvements over the previous 1.0.8 GA release.
MariaDB ColumnStore 1.0.9 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 mariadb-columnstore@googlegroups.com
MCOL-529 - Adds message queue pooling to prevent port exhaustion under some cases of high volume transactional DML statements.
MCOL-706 - ColumnStore has been updated to the 10.1.23 version of MariaDB Server.
MDEV-12673 - Additional bug fix to MariaDB server resolving a server crash under certain query patterns.
MCOL-529 - DBRM message queue clients need to be pooled
MCOL-650 - stored procedures with queries invoked over odbc prepared statements take very long
MCOL-652 - Derived tables in a join subquery cause error
MCOL-653 - sum function provides different results between innodb and columnstore
MCOL-655 - Debugging symbols are missing
MCOL-656 - Error in LIKE behaviour
MCOL-657 - Support NULL safe equals (<=>)
MCOL-679 - Crash on prepared statement when no parameters bound
MCOL-683 - ADDDATE & DATE_FORMAT combo breaks datetime
MCOL-693 - Segmentation Fault with non-string SP parameter
MCOL-704 - Using BETWEEN together with date functions in WHERE clause 100x slower than InfiniDB
MCOL-706 - Merge 10.1.23 into 1.0.9
MDEV-12673 - Server crashes in create_ref_for_key
Multi version upgrades are not supported, please upgrade versions prior to 1.0.8 before upgrading to 1.0.9:
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.9 GA version.
The supported OS for the GA version are CentOS 6, CentOS 7, Debian 8.6, RedHat 6, RedHat 7, SUSE 12, 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.9". AMI specific installation instructions can be found here.
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 - Source code for engine specific processes on UM and PM node
This page is: Copyright © 2025 MariaDB. All rights reserved.