MariaDB ColumnStore 1.0.12 GA Release Notes
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
Notable changes
Bugs and issues fixed
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
Upgrade
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).
Known issues and limitations
There are a number bugs and known limitations within this version of MariaDB ColumnStore, the most serious of these are listed below.
MCOL-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.
Documentation
MariaDB ColumnStore Documentation
Packaging
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.
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
Storage Engine - Source code for engine specific processes on UM and PM node
This page is: Copyright © 2025 MariaDB. All rights reserved.
Last updated
Was this helpful?