Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Release notes for MariaDB ColumnStore 25.10
Release notes for MariaDB ColumnStore 23.10
MariaDB ColumnStore and CMAPI release notes
MariaDB Enterprise ColumnStore 23.10.7 is a maintenance release of MariaDB Enterprise ColumnStore. MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server.
MariaDB Enterprise ColumnStore 23.10.7 was released on 13 November 2025. This release is of General Availability (GA) maturity. MariaDB Enterprise ColumnStore 23.10.7 is a GA release in the 23.10 series.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.6.23-19 and MariaDB Enterprise Server 11.4.8-5.
MariaDB ColumnStore 23.10.5 is a maintenance release of MariaDB ColumnStore.
MariaDB ColumnStore 23.10.5 was released on 6 August 2025. This release is of General Availability (GA) maturity. MariaDB ColumnStore 23.10.5 is a GA release in the 23.10 series.
This release of MariaDB ColumnStore is included with MariaDB Community Server 12.0.2, 11.8.3, and 11.4.8.
MariaDB Enterprise ColumnStore 23.10.6 is a maintenance release of MariaDB Enterprise ColumnStore. MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server.
MariaDB Enterprise ColumnStore 23.10.6 was released on 8 September 2025. This release is of General Availability (GA) maturity. MariaDB Enterprise ColumnStore 23.10.6 is a GA release in the 23.10 series.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.6.23-19 and MariaDB Enterprise Server 11.4.8-5.
Release notes for MariaDB ColumnStore 23.02
Release notes for MariaDB ColumnStore 22.08
Release notes for MariaDB ColumnStore 6
Release notes for MariaDB ColumnStore 5.5
Release notes for the MariaDB ColumnStore Cluster Management API (CMAPI)
Old release notes for MariaDB ColumnStore releases
Release notes for MariaDB ColumnStore 5.6
Release notes for MariaDB ColumnStore 1.1
Release notes for MariaDB ColumnStore 1.0
Release notes for MariaDB ColumnStore 1.4
[MCOL-4605] - FROM_UNIXTIME(negativeDecimal) not behaving as InnoDB
[MCOL-4905] - make log message "Got a 4xx error" more verbose
[MCOL-6194] - Cmapi user configurable failover no response wait time
[MCOL-5843] - initialize extent min/max with reasonable values
[] - make timeout configurable " A node is unresponsive for cmd = 4, no reconfigure in at least 300 seconds. Setting read-only mode."
[] - deactivate_only logic is always enabled on node removal in CMAPI
[] - Extremely large primloc logs generated after upgrade from 23.10.3 to 23.10.4
[MCOL-5756] - Handle UNION pushdown edge case that triggers slow table mode processing
In alignment with the enterprise lifecycle, MariaDB Enterprise ColumnStore 23.10.6 is provided for:
Debian 11 (x86_64, ARM64)
Debian 12 (x86_64, ARM64)
Red Hat Enterprise Linux 8 (x86_64, ARM64)
Red Hat Enterprise Linux 9 (x86_64, ARM64)
Red Hat Enterprise Linux 10 (x86_64, ARM64)
Rocky Linux 8 (x86_64, ARM64)
Rocky Linux 9 (x86_64, ARM64)
Ubuntu 22.04 (x86_64, ARM64)
Ubuntu 24.04 (x86_64, ARM64)
Compilation fixes for the community server.
There are no issues fixed in this release.
MariaDB ColumnStore 23.10.5 is provided for:
Debian 11 (x86_64, ARM64)
Debian 12 (x86_64, ARM64)
Red Hat Enterprise Linux 8 (x86_64, ARM64)
Red Hat Enterprise Linux 9 (x86_64, ARM64)
Rocky Linux 8 (x86_64, ARM64)
Rocky Linux 9 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, ARM64)
Ubuntu 22.04 (x86_64, ARM64)
Ubuntu 24.04 (x86_64, ARM64)
cpimport: Add a -header option to skip a specified number of rows. (MCOL-4882)
cpimport: Enhance error handling to log all failed records to a specified file. (MCOL-5164)
S3: Add a verbose option to testS3Connection for more detailed output. (MCOL-4833)
CMAPI: Clarify cluster_mode status when ColumnStore is offline to reduce confusion. (MCOL-5988)
Error Messaging: Add a more verbose error message for "unable to open Buffered file". (MCOL-4869)
Logging: Enhance logging to improve the new user experience. (MCOL-5877)
Error Messaging: Log the table name when a table does not exist in ColumnStore for a more verbose error message. (MCOL-5915)
CMAPI: Include log collection tools with CMAPI. (MCOL-5300)
Platforms: Add build support for Red Hat Enterprise Linux 10 and packaging for SELinux policies. (MCOL-6155)
Can result in hang or crash
Timeout issue when BRM_savesB_journal is not found. (MCOL-5338)
cmapi writes the local loopback address (127.0.1.1) instead of the real IP address. (MCOL-5913)
CMAPI fails to remove a node from the cluster. (MCOL-6147)
Increase the default cpimport batch size to 8,000,000 to match the maximum extent size. (MCOL-6033)
In alignment with the enterprise lifecycle, MariaDB Enterprise ColumnStore 23.10.6 is provided for:
Debian 11 (x86_64, ARM64)
Debian 12 (x86_64, ARM64)
Red Hat Enterprise Linux 8 (x86_64, ARM64)
Red Hat Enterprise Linux 9 (x86_64, ARM64)
Red Hat Enterprise Linux 10 (x86_64, ARM64)
Rocky Linux 8 (x86_64, ARM64)
Rocky Linux 9 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, ARM64)
Ubuntu 22.04 (x86_64, ARM64)
Ubuntu 24.04 (x86_64, ARM64)
MariaDB Enterprise ColumnStore 23.10.2 is a feature release of MariaDB Enterprise ColumnStore. MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server.
MariaDB Enterprise ColumnStore 23.10.2 was released on 2024-08-19. This release is of General Availability (GA) maturity. MariaDB Enterprise ColumnStore 23.10.2 is a GA release in the 23.10 series.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.6.18-14.
Save EM image locally if S3 fails PUT request or avoid saving if shared memory image is damaged or empty ()
No data gets loaded into BLOB column and the value is left NULL ()
Using regexp_substr on table with engine=columnstore results in error:"Function 'regexp_substr' isn't supported." ()
ORDER BY clause if not included in the GROUP BY clause fails ()
Group By ... Order By NULL fails ()
Alter table add column leaves table unusable ()
select * into file from (select ... group by) produces spurious error ()
CMAPI: ConnectionRefusedError unhandled exception ()
Truncate table failed after PrimProc restarted ()
mcs-savebrm stores an empty EM on cluster shutdown rendering the cluster unusable ()
NULL & non-zero length string, assertion 'mStr || mLength == 0' failed ()
Disk join step race with parallel join (more than one thread) ()
In alignment with the , MariaDB Enterprise ColumnStore 23.10.2 is provided for:
Debian 11 (x86_64, ARM64)
Debian 12 (x86_64, ARM64)
Red Hat Enterprise Linux 8 (x86_64, ARM64)
Red Hat Enterprise Linux 9 (x86_64, ARM64)
Upgrade Multi-Node MariaDB Enterprise ColumnStore from 6 to 23.10
MariaDB Enterprise ColumnStore 23.10.4 is a maintenance release of MariaDB Enterprise ColumnStore. MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server.
MariaDB Enterprise ColumnStore 23.10.4 was released on 19 May 2025. This release is of General Availability (GA) maturity. MariaDB Enterprise ColumnStore 23.10.4 is a GA release in the 23.10 series.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.6.21-17.
23.02.14 is a maintenance release of . MariaDB Enterprise ColumnStore is a columnar storage engine that is included with the .
MariaDB Enterprise ColumnStore 23.02.14 was released on 7 May 2025. This release is of General Availability (GA) maturity. MariaDB Enterprise ColumnStore 23.02.14 is a GA release in the 23.02 series.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.6.14-9.
Users of earlier MariaDB Enterprise ColumnStore releases are encouraged to upgrade.
Cluster Management API (CMAPI) 22.08.2 is a maintenance release of CMAPI. CMAPI is a REST API for administering in multi-node topologies.
Cluster Management API 22.08.2 was released on 2022-11-15. This release is of General Availability (GA) maturity.
CMAPI 22.08.2 is compatible with MariaDB Enterprise ColumnStore 22.08. CMAPI 22.08.2 was first released with
Users of CMAPI 22.08.1 are encouraged to upgrade.
6.4.8 is a maintenance release of . MariaDB ColumnStore is a columnar storage engine included with MariaDB Enterprise Server and MariaDB Community Server 10.6, 10.11, and 11.0. This is a release in the ColumnStore 6 series.
MariaDB Enterprise ColumnStore 6.4.8 was released on 2024-02-07. This release is of General Availability (GA) maturity.
This release of MariaDB ColumnStore is included with MariaDB Community Server 10.11.7 and MariaDB Community Server 10.6.17
6.4.6 is a maintenance release of . MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server. This is the seventh release in the Enterprise ColumnStore 6 series.
MariaDB Enterprise ColumnStore 6.4.6 was released on 2022-09-30. This release is of General Availability (GA) maturity.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.6.8-4.
6.4.4 is a maintenance release of . MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server. This is the sixth release in the Enterprise ColumnStore 6 series.
MariaDB Enterprise ColumnStore 6.4.4 was released on 2022-08-09. This release is of General Availability (GA) maturity.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.6.8-4.
5.6.8 is a maintenance release of . MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server.
MariaDB Enterprise ColumnStore 5.6.8 was released on 2022-12-21. This release is of General Availability (GA) maturity.
This release of MariaDB Enterprise ColumnStore is included starting with MariaDB Enterprise Server 10.5.18-13.
5.6.7 is a maintenance release of . MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server.
MariaDB Enterprise ColumnStore 5.6.7 was released on 2022-09-12. This release is of General Availability (GA) maturity.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.5.17-12.
Release notes for MariaDB ColumnStore 5.4.
Release notes for MariaDB ColumnStore 1.5
Release notes for MariaDB ColumnStore 1.2
MariaDB Columnstore all versions: update and inserts behave differently on 0000-00-00 00:00:00 datetime (MCOL-5035)
Cross-Engine join at text type not supported (MCOL-5056)
ColumnStore table does not exist after a rename (MCOL-5197)
Using views leads to an error when an Analyzer report with a measure and a year is built. (MCOL-5236)
Views with null-replaced timestamps yield incorrect query results (MCOL-5237)
RAND() uses static seed of 0 (MCOL-5492)
Resultset will be cut with setting columnstore_um_mem_limit >0 (MCOL-5689)
CS return error for intersect (MCOL-5699)
Random columnstore error MCS-2035 with special SELECT structures (MCOL-5704)
Rocky Linux 9 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, ARM64)
Ubuntu 22.04 (x86_64, ARM64)
Ubuntu 24.04 (x86_64, ARM64)
New memory consumption accounting mechanism to prevent OOM events-related crashes. (MCOL-5797)
FROM_UNIXTIME(negativeDecimal) not behaving as InnoDB (MCOL-4605)
SEC_TO_TIME(wideDecimal) returns 0 in DECIMAL context (MCOL-4607)
MOD loses precision on huge narrow decimal (MCOL-4611)
Different results compared to innodb with union all and subselect with null in select and impossible where condition ()
cmapi support for log collection ()
JSON_ARRAYAGG in MCS works differently than in InnoDB. ()
CLI Startup - Single start command for Single Node ()
Alias "mcs CLUSTER" commands to just mcs ()
Cmapi (mcs cli) support for columnstore backups ()
Improve Client Error Messaging and async broadcasting config. ()
CTE/aggreation function give wrong results ()
DROP TABLE IF EXISTS should not generate errors for non existing tables ()
Disk based GROUP_CONCAT() ()
NULLIF function returns -32768 instead of NULL when querying a Columnstore table ()
when a value of a column is empty text ('') the result of group_concat(json_object(...)) is null instead of the correct result set ()
Creating different keys with cskeys on all nodes can break cluster(key not distributed properly) (MCOL-5019)
Bitwise aggregation functions do not work with wide decimals (internal error) (MCOL-5386)
Loss of PrimProc can lead to infinite loop (MCOL-5396)
GROUP_CONCAT in query uses enormous amount of RAM causing OOM to kill PrimProc (MCOL-5852)
mariadbd crashing randomly when running "SELECT calShowPartitions(" ()
SubAdapterStep::execute() MCS-2035 Fix Requested ()
primproc oversubscribes memory ()
primproc 11/SEGV - querying a view ()
Fix rollbacks in mcs cli and passing errors during broadcasting config. ()
Subselect sorting is single-threaded always (MCOL-5316)
In alignment with the enterprise lifecycle, MariaDB Enterprise ColumnStore 23.10.3 is provided for:
Debian 11 (x86_64, ARM64)
Debian 12 (x86_64, ARM64)
Red Hat Enterprise Linux 8 (x86_64, ARM64)
Red Hat Enterprise Linux 9 (x86_64, ARM64)
Rocky Linux 8 (x86_64, ARM64)
Rocky Linux 9 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, ARM64)
Ubuntu 22.04 (x86_64, ARM64)
Ubuntu 24.04 (x86_64, ARM64)
Printing of the internal ExtentMap structure to stdout has been removed
In alignment with the enterprise lifecycle, MariaDB Enterprise ColumnStore 23.02.14 is provided for:
Debian 11 (x86_64, ARM64)
Red Hat Enterprise Linux 8 (x86_64, ARM64)
Red Hat Enterprise Linux 9 (x86_64, ARM64)
Rocky Linux 8 (x86_64, ARM64)
Rocky Linux 9 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, ARM64)
Ubuntu 22.04 (x86_64, ARM64)
Upgrade Multi-Node MariaDB Enterprise ColumnStore from 6 to 23.10
The cluster is not correctly reconfigured when a PM fails and recovers: (MCOL-5286)
DDL will fail after a PM fails.
Selects will fail after the PM recovers.
In alignment to the MariaDB Corporation Engineering Policy, CMAPI 22.08.2 is provided for:
CentOS 7 (x86_64)
Debian 11 (x86_64, ARM64)
Red Hat Enterprise Linux 7 (x86_64)
Red Hat Enterprise Linux 8 (x86_64, ARM64)
Red Hat Enterprise Linux 9 (x86_64, ARM64)
Rocky Linux 8 (x86_64, ARM64)
Rocky Linux 9 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, ARM64)
Ubuntu 22.04 (x86_64, ARM64)
This page is: Copyright © 2025 MariaDB. All rights reserved.
In alignment with the enterprise lifecycle, MariaDB ColumnStore 6.4.8 is provided for:
CentOS 7 (x86_64)
Debian 10 (x86_64)
Red Hat Enterprise Linux 7 (x86_64)
Red Hat Enterprise Linux 8 (x86_64)
Rocky Linux 8 (x86_64)
Ubuntu 18.04 (x86_64)
Ubuntu 20.04 (x86_64)
This page is: Copyright © 2025 MariaDB. All rights reserved.
An error can be returned during disk aggregation. (MCOL-5213)
The following error message could be raised to the client:
GROUP BY can return duplicates. (MCOL-5213)
In alignment to the enterprise lifecycle, MariaDB Enterprise ColumnStore 6.4.6 is provided for:
CentOS 7 (x86_64)
Debian 10 (x86_64)
Red Hat Enterprise Linux 7 (x86_64)
Red Hat Enterprise Linux 8 (x86_64)
Rocky Linux 8 (x86_64)
Ubuntu 18.04 (x86_64)
Ubuntu 20.04 (x86_64)
This page is: Copyright © 2025 MariaDB. All rights reserved.
When disk-based aggregations are enabled, aggregations can fail with the ER_INTERNAL_ERROR error code. (MCOL-5153)
The following error message could be raised to the client:
In alignment with the enterprise lifecycle, MariaDB Enterprise ColumnStore 6.4.4 is provided for:
CentOS 7 (x86_64)
Debian 10 (x86_64)
Red Hat Enterprise Linux 7 (x86_64)
Red Hat Enterprise Linux 8 (x86_64)
Rocky Linux 8 (x86_64)
Ubuntu 18.04 (x86_64)
Ubuntu 20.04 (x86_64)
This page is: Copyright © 2025 MariaDB. All rights reserved.
Miscellaneous minor build and bug fixes
In alignment with the enterprise lifecycle, MariaDB Enterprise ColumnStore 5.6.8 is provided for:
CentOS 7 (x86_64)
Debian 10 (x86_64)
Red Hat Enterprise Linux 7 (x86_64)
Red Hat Enterprise Linux 8 (x86_64)
Ubuntu 18.04 (x86_64)
Ubuntu 20.04 (x86_64)
Miscellaneous minor build and bug fixes
In alignment with the enterprise lifecycle, MariaDB Enterprise ColumnStore 5.6.7 is provided for:
CentOS 7 (x86_64)
Debian 10 (x86_64)
Red Hat Enterprise Linux 7 (x86_64)
Red Hat Enterprise Linux 8 (x86_64)
Ubuntu 18.04 (x86_64)
Ubuntu 20.04 (x86_64)
Major Release Upgrades for MariaDB Enterprise ColumnStore.
MariaDB ColumnStore, the columnar storage engine optimized for Online Analytical Processing (OLAP) workloads, enhances MariaDB Platform 2026 with advanced hybrid transactional-analytical processing (HTAP) capabilities. Its massively parallel processing (MPP) architecture enables real-time analytics directly on live InnoDB transactional data, eliminating the need for separate data pipelines or delayed imports. Tightly integrated with MariaDB Enterprise Server, ColumnStore supports parallel execution of complex analytical queries alongside transactional workloads, delivering instant insights from dynamic datasets. With enhanced scalability, streamlined cluster management, and robust data handling, ColumnStore in the 2026 Platform is the ideal solution for enterprises seeking seamless, high-performance analytics and transactional processing in modern data-driven applications.
Major improvements relative to previous release series include:
Scalability & Performance
Horizontal scaling option via read-only nodes
New bulk loading import flags and improvements
Operations & Usability
On failover, metadata could become corrupted when looking for a file that's not supposed to exist called BRM_savesB_journal.
cpimport maximum batch size -q raised to 8,000,000
Disk-based distinct []
Post upgrade to 23.10.4, some of the queries giving different set of results upon executing multiple times []
Extremely large primloc logs generated after upgrade from 23.10.3 to 23.10.4 []
Deactivate_only logic is always enabled on node removal in CMAPI []
Selinux rules needed to enable columnstore for rhel 10 []
Added ORDER BY and LIMIT/OFFSET processing for UNION queries. Handle UNION pushdown edge case that triggers slow table mode processing []
Read-replica Columnstore nodes v1 []
MariaDB Enterprise ColumnStore 23.10.1 is a feature release of MariaDB Enterprise ColumnStore. MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server.
MariaDB Enterprise ColumnStore 23.10.1 was released on 2024-03-11. This release is of General Availability (GA) maturity. MariaDB Enterprise ColumnStore 23.10.1 is a GA release in the 23.10 series.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.6.17-12.
The changes listed here are relative to MariaDB Enterprise ColumnStore 23.02.4.
Cross db table rename fails ()
Columnstore throws error when using GROUP BY on DB-Views where field name is identical in two different tables ()
GROUP BY on duplicate expressions using functions throws error "IDB-2001: ... is not in GROUP BY clause." on Columnstore ()
Support WITH ROLLUP ()
Shmem segment remap causes SEGV in ExtentMapIndexImpl::find ()
Queries stuck in MariaDB waiting for an answer from PrimProc ()
LIKE '%1%' in WHERE part never finishes ()
PrimProc goes in a loop, 100% CPU usage on a single core ()
PrimProc crashes in json_key_matches ()
UPDATE returns wrong "Rows matched" on multi-tables ()
json data returns differently by same query ()
Columnstore query returns incorrect value instead of expected out-of-range error ()
JSON_QUERY is stateful (may segfault on big amount of data) ()
CPU wastes time in wait and sys because of urandom access in RowStorage ()
Wrong metadata in CMAPI packages ()
In alignment with the , MariaDB Enterprise ColumnStore 23.10.1 is provided for:
Debian 11 (x86_64, ARM64)
Debian 12 (x86_64, ARM64)
Red Hat Enterprise Linux 8 (x86_64, ARM64)
Red Hat Enterprise Linux 9 (x86_64, ARM64)
Upgrade Multi-Node MariaDB Enterprise ColumnStore from 6 to 23.10
MariaDB Enterprise ColumnStore 23.02.15 is a maintenance release of MariaDB Enterprise ColumnStore. MariaDB Enterprise ColumnStore is a columnar storage engine that is included with the MariaDB Enterprise Server.
MariaDB Enterprise ColumnStore 23.02.15 was released on 3 Jul 2025. This release is of General Availability (GA) maturity. MariaDB Enterprise ColumnStore 23.02.15 is a GA release in the 23.02 series.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.6.14-9 and 10.6.15-10.
Users of earlier MariaDB Enterprise ColumnStore releases are encouraged to upgrade.
Backport to 23.02 and release 23.02 using ES 10.6.15-10.
In alignment with the , MariaDB Enterprise ColumnStore 23.02.14 is provided for:
Debian 11 (x86_64, ARM64)
Red Hat Enterprise Linux 8 (x86_64, ARM64)
Red Hat Enterprise Linux 9 (x86_64, ARM64)
Rocky Linux 8 (x86_64, ARM64)
Upgrade Multi-Node MariaDB Enterprise ColumnStore from 6 to 23.10
MariaDB Enterprise ColumnStore 22.08.4 is a maintenance release of MariaDB Enterprise ColumnStore. MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server.
MariaDB Enterprise ColumnStore 22.08.4 was released on 2022-11-15. This release is of General Availability (GA) maturity.
MariaDB Enterprise ColumnStore 22.08 replaces MariaDB Enterprise ColumnStore 6 in MariaDB Enterprise Server 10.6.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.6.9-5.
Users of earlier MariaDB Enterprise ColumnStore 22.08 releases are encouraged to upgrade.
With MariaDB Replication and ColumnStore, queries on a replica will hang. ()
In alignment with the , MariaDB Enterprise ColumnStore 22.08.4 is provided for:
CentOS 7 (x86_64)
Debian 11 (x86_64, ARM64)
Red Hat Enterprise Linux 7 (x86_64)
Red Hat Enterprise Linux 8 (x86_64, ARM64)
Upgrade Multi-Node MariaDB Enterprise ColumnStore from 6 to 23.10
MariaDB Enterprise ColumnStore 22.08.3 is a maintenance release of MariaDB Enterprise ColumnStore. MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server.
MariaDB Enterprise ColumnStore 22.08.3 was released on 2022-11-05. This release is of General Availability (GA) maturity.
MariaDB Enterprise ColumnStore 22.08 replaces MariaDB Enterprise ColumnStore 6 in MariaDB Enterprise Server 10.6.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.6.9-5.
Users of MariaDB Enterprise ColumnStore 22.08.1 or 22.08.2 are encouraged to upgrade.
With multi-node deployments, queries can hang on one node. ()
In alignment with the , MariaDB Enterprise ColumnStore 22.08.3 is provided for:
CentOS 7 (x86_64)
Debian 10 (x86_64, ARM64)
Debian 11 (x86_64, ARM64)
Red Hat Enterprise Linux 7 (x86_64)
Upgrade Multi-Node MariaDB Enterprise ColumnStore from 6 to 23.10
Cluster Management API (CMAPI) 22.08.1 is a maintenance release of CMAPI. CMAPI is a REST API for administering MariaDB Enterprise ColumnStore in multi-node topologies.
Cluster Management API 22.08.1 was released on 2022-09-12. This release is of General Availability (GA) maturity.
CMAPI 22.08.1 is compatible with MariaDB Enterprise ColumnStore 22.08. CMAPI 22.08.1 was first released with MariaDB Enterprise ColumnStore 22.08.1.
CMAPI configures ColumnStore to allow read queries to be executed on any node. ()
In previous releases, CMAPI only added an ExeMgr section for the primary node to Columnstore.xml.
Starting with this release, CMAPI adds an ExeMgr section for every node to Columnstore.xml, which means that any node can execute read queries.
Since Enterprise ColumnStore 22.08 merges the ExeMgr process into the PrimProc process, CMAPI no longer tries to start ExeMgr on a node when the binary is not present. ()
Some redundant log messages have been removed from the CMAPI log. ()
In alignment to the MariaDB Corporation Engineering Policy, CMAPI 22.08.1 is provided for:
CentOS 7 (x86_64)
Debian 10 (x86_64, ARM64)
Debian 11 (x86_64, ARM64)
Red Hat Enterprise Linux 7 (x86_64)
This page is: Copyright © 2025 MariaDB. All rights reserved.
Cluster Management API (CMAPI) 1.6.3 is a maintenance release of CMAPI. CMAPI is a REST API for administering MariaDB Enterprise ColumnStore in multi-node topologies.
Cluster Management API 1.6.3 was released on 2022-04-20. This release is of General Availability (GA) maturity.
CMAPI 1.6.3 is compatible with MariaDB Enterprise ColumnStore 5.6 and 6. CMAPI 1.6.3 was first released with MariaDB Enterprise ColumnStore 5.6.5 and MariaDB Enterprise ColumnStore 6.2.3.
When a node is added to the cluster using a DNS name, the node's DNS name is added to Columnstore.xml instead of the node's IP address. ()
Prior to this release, when a node's IP address changed after it was added to the cluster, Columnstore.xml still contained the node's old IP address.
Starting with this release, CMAPI can adapt to changing IP addresses when the DNS name in Columnstore.xml resolves to the new IP address.
After the primary server is killed and restarted, MaxScale and CMAPI could each choose different primary servers. ()
In alignment to the MariaDB Corporation Engineering Policy, CMAPI 1.6.3 is provided for:
CentOS 7 (x86_64)
Debian 10 (x86_64)
Red Hat Enterprise Linux 7 (x86_64)
Red Hat Enterprise Linux 8 (x86_64)
This page is: Copyright © 2025 MariaDB. All rights reserved.
Cluster Management API (CMAPI) 1.6.2 is a maintenance release of CMAPI. CMAPI is a REST API for administering MariaDB Enterprise ColumnStore in multi-node topologies.
Cluster Management API 1.6.2 was released on 2022-02-23. This release is of General Availability (GA) maturity.
CMAPI 1.6.2 is compatible with MariaDB Enterprise ColumnStore 5.6 and 6. CMAPI 1.6.2 was first released with MariaDB Enterprise ColumnStore 5.6.5 and MariaDB Enterprise ColumnStore 6.2.3.
Compatibility added for MariaDB ColumnStore 6.2.3. ()
Compatibility added for Enterprise ColumnStore 6.2.3 cross engine join encrypted passwords. ()
Added support for using a custom port for cross engine join support. ()
During upgrade CMAPI configuration information is lost. Customer data is not impacted. ()
mcsStatus incorrectly returns "cluster_mode": null. This is a cosmetic issue that does not affect operation. ()
In alignment to the MariaDB Corporation Engineering Policy, CMAPI 1.6.2 is provided for:
CentOS 7 (x86_64)
Debian 10 (x86_64)
Red Hat Enterprise Linux 7 (x86_64)
Red Hat Enterprise Linux 8 (x86_64)
This page is: Copyright © 2025 MariaDB. All rights reserved.
MariaDB Enterprise ColumnStore 6.4.2 is a maintenance release of MariaDB Enterprise ColumnStore . MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server. This is the sixth release in the Enterprise ColumnStore 6 series.
MariaDB Enterprise ColumnStore 6.4.2 was released on 2022-07-19. This release is of General Availability (GA) maturity.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.6.8-4.
When disk-based aggregations are enabled, aggregations can fail with the ER_INTERNAL_ERROR error code. ()
The following error message could be raised to the client:
This change was a speculative bug fix. Please use Enterprise ColumnStore 6.4.4 or later for the complete bug fix.
In alignment with the , MariaDB Enterprise ColumnStore 6.4.2 is provided for:
CentOS 7 (x86_64)
Debian 10 (x86_64)
Red Hat Enterprise Linux 7 (x86_64)
Red Hat Enterprise Linux 8 (x86_64)
This page is: Copyright © 2025 MariaDB. All rights reserved.
MariaDB Enterprise ColumnStore 6.2.3 is a maintenance release of MariaDB Enterprise ColumnStore. MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server. This is the third release in the Enterprise ColumnStore 6 series.
MariaDB Enterprise ColumnStore 6.2.3 was released on 2022-02-23. This release is of General Availability (GA) maturity.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.6.5-2 and MariaDB Enterprise Server 10.6.7-3.
CMAPI 1.6.2 was originally included
CMAPI 1.6.3 is now included
CMAPI is a REST API for administering MariaDB Enterprise ColumnStore in multi-node topologies.
For additional information, see "Release Notes for CMAPI 1.6.2" and "Release Notes for CMAPI 1.6.3".
UPDATE with cross engine IN subquery produced unexpected results. ()
Error can arise with cross engine JOIN: Internal error: CrossEngineStep::execute() caught getSignedNullValue(): got bad column width (4) ()
IN operation doesn't respect COLLATE ()
Slower than expected bulk insertion. ()
In alignment with the , MariaDB Enterprise ColumnStore 6.2.3 is provided for:
CentOS 7 (x86_64)
Debian 10 (x86_64)
Red Hat Enterprise Linux 7 (x86_64)
Red Hat Enterprise Linux 8 (x86_64)
This page is: Copyright © 2025 MariaDB. All rights reserved.
MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise ColumnStore. This is the sixth release in the Enterprise ColumnStore 5 series.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.5.10-7.
This release is of General Availability (GA) maturity.
MariaDB Enterprise ColumnStore 5.6.2 was released on 2021-06-30.
Possible segfault with disk-based aggregation. (, )
In alignment with the , MariaDB Enterprise ColumnStore 5.6.2 is provided for:
CentOS 7
CentOS 8
Debian 9
Debian 10
Major Release Upgrades for MariaDB Enterprise ColumnStore.
23.02.9 is a maintenance release of . MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server.
MariaDB Enterprise ColumnStore 23.02.9 was released on 2024-08-19. This release is of General Availability (GA) maturity. MariaDB Enterprise ColumnStore 23.02.9 is a GA release in the 23.02 series.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.6.14-9.
Users of earlier MariaDB Enterprise ColumnStore releases are encouraged to upgrade.
23.02.8 is a maintenance release of . MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server.
MariaDB Enterprise ColumnStore 23.02.8 was released on 2024-02-16. This release is of General Availability (GA) maturity. MariaDB Enterprise ColumnStore 23.02.8 is the fourth GA release in the 23.02 series.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.6.14-9.
Users of earlier MariaDB Enterprise ColumnStore releases are encouraged to upgrade.
23.02.2 is a maintenance release of . MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server.
MariaDB Enterprise ColumnStore 23.02.2 was released on 2023-04-14. This release is of General Availability (GA) maturity. MariaDB Enterprise ColumnStore 23.02.2 is the second GA release in the 23.02 series.
MariaDB Enterprise ColumnStore 23.02 replaces MariaDB Enterprise ColumnStore 22.08 in MariaDB Enterprise Server 10.6.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.6.12-7.
Users of earlier MariaDB Enterprise ColumnStore releases are encouraged to upgrade.
22.08.2 is a maintenance release of . MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server.
MariaDB Enterprise ColumnStore 22.08.2 was released on 2022-10-04. This release is of General Availability (GA) maturity.
MariaDB Enterprise ColumnStore 22.08 replaces MariaDB Enterprise ColumnStore 6 in MariaDB Enterprise Server 10.6.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.6.9-5.
This release has been withdrawn. Users of MariaDB Enterprise ColumnStore 22.08.2 should upgrade to MariaDB Enterprise ColumnStore 22.08.3.
Cluster Management API (CMAPI) 6.4.1 is a maintenance release of CMAPI. CMAPI is a REST API for administering in multi-node topologies.
Cluster Management API 6.4.1 was released on 2022-07-12. This release is of General Availability (GA) maturity.
CMAPI 6.4.1 is compatible with MariaDB Enterprise ColumnStore 6. CMAPI 6.4.1 was first released with
Cluster Management API (CMAPI) 1.6.0 is a maintenance release of . CMAPI is a REST API for administering in multi-node topologies.
Cluster Management API 1.6.0 was released on 2021-12-13. This release is of General Availability (GA) maturity.
CMAPI 1.6.0 is compatible with MariaDB Enterprise ColumnStore 5.6 and 6. CMAPI 1.6.0 was first released with and
6.4.1 is a maintenance release of . MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server. This is the fifth release in the Enterprise ColumnStore 6 series.
MariaDB Enterprise ColumnStore 6.4.1 was released on 2022-07-12. This release is of General Availability (GA) maturity.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.6.8-4.
6.3.1 is a maintenance release of . MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server. This is the fourth release in the Enterprise ColumnStore 6 series.
MariaDB Enterprise ColumnStore 6.3.1 was released on 2022-04-25. This release is of General Availability (GA) maturity.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.6.7-3.
5.6.5 is a maintenance release of . MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server. This is the eighth release in the Enterprise ColumnStore 5 series.
MariaDB Enterprise ColumnStore 5.6.5 was released on 2022-02-14. This release is of General Availability (GA) maturity.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.5.13-9 and MariaDB Enterprise Server 10.5.15-10.
5.6.3 is a maintenance release of . MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server. This is the seventh release in the Enterprise ColumnStore 5 series.
MariaDB Enterprise ColumnStore 5.6.3 was released on 2021-12-13. This release is of General Availability (GA) maturity.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.5.13-9.
MCS-2056: There was an IO error during a disk-based aggregation: No such file or directoryERROR 1815 (HY000): Internal error: TupleAggregateStep::threadedAggregateRowGroups()[24] MCS-2054: Unknown error while aggregation.Added encrypted password support for the cross engine join user. (MCOL-4946)
A ColumnStore process thread read call could last indefinitely. (MCOL-4927)
With this release, if no data appears when a ColumnStore process thread makes a read call, the thread logs an error, closes the socket, and proceeds.
Prior to this release, a ColumnStore process thread would synchronously wait for data to appear in the socket.
QueryStats does not automatically log each query to calGetTrace() results. (MCOL-4944)
With this release, when QueryStats is enabled, queries are automatically logged to infinidb_querystats.querystats
Prior to this release, it was necessary to execute SELECT calGetTrace(1) to log queries even with QueryStats enabled.
Ubuntu 20.04 (x86_64)
Deprecated and historical values have been removed from Columnstore.xml (MCOL-4560)
Segfault in Storage Manager due to thread limits. (MCOL-3983)
Segfault when using distributed aggregate functions. (MCOL-4807)
Segfault during cpimport to table with large column count. (MCOL-4974)
ExeMgr crashes after a large join, resulting in client-side error ERROR 1815 (HY000): Internal error: IDB-2004: Cannot connect to ExeMgr. (MCOL-4841)
ROUND() on DOUBLE in case statements in conjunction with subqueries can generate incorrect value. (MCOL-4940)
CRC32(), when called with two arguments, against a ColumnStore table, returns the wrong value. (MCOL-4966)
A query with filter condition on subquery with window function can return the wrong result. (MCOL-4570)
Incorrect help text. (MCOL-4834)
On Debian, non-interactive upgrade complains that /etc/columnstore/Columnstore.xml has been modified since installation. (MCOL-4928)
Upgrade from ColumnStore 5 to ColumnStore 6 does not restore saved configuration files. (MCOL-4965)
Prior to this release, configuration files were saved at uninstall but not restored upon upgrade.
With this release, ColumnStore configuration files are properly restored upon reinstall. New parameters, included in the configuration files packaged with the release, will not be merged and must be migrated manually.
With this release, when manually upgrading (uninstall and reinstall), the server.cnf is replaced with the packaged copy.
With this release, when upgrading by repository, the existing server.cnf is retained.
In alignment with the enterprise lifecycle, MariaDB Enterprise ColumnStore 6.3.1 is provided for:
CentOS 7 (x86_64)
Debian 10 (x86_64)
Red Hat Enterprise Linux 7 (x86_64)
Red Hat Enterprise Linux 8 (x86_64)
Ubuntu 18.04 (x86_64)
Ubuntu 20.04 (x86_64)
This page is: Copyright © 2025 MariaDB. All rights reserved.
Ubuntu 18.04 (x86_64)
Ubuntu 20.04 (x86_64)
ERROR 1815 (HY000): Internal error: TupleAggregateStep::threadedAggregateRowGroups()[24] MCS-2054:
Unknown error while aggregation.New, simplified upgrade process
LOAD DATA INFILE IGNORE. Before, you had to define a number of errors, and users tended to set it to a really high number like 99999.-L
Rows that produce an error are now stored separately into a new file, so you can easily and quickly review what failed and reimport just the failed records. Previously, you would not know which specific records failed, requiring to do your own analysis of what was imported versus skipped.
mcs backup --help and mcs restore --help
Back up and restore your ColumnStore database easier than ever. External scripts to manage those operations are no longer needed, because CMAPI includes it. Example: mcs dbrm_backup
MCOL-5480 test failure with 11.4 [MCOL-5974]
Make timeout configurable " A node is unresponsive for cmd = 4, no reconfigure in at least 300 seconds. Setting read-only mode." [MCOL-5508]
Initialize extent min/max with reasonable values [MCOL-5843]
mcs cluster node add --node $pm2 --read-replicaFairThreadScheduler::sendErrorMsg and BPPSeeder::sendErrorMsg crash PP trying to send to a nullptr sock (MCOL-5636)
Continuous workload triggers unknown primitive cmd message in PP log (MCOL-5637)
Rocky Linux 9 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, ARM64)
Ubuntu 22.04 (x86_64, ARM64)
Ubuntu 24.04 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, ARM64)
Ubuntu 22.04 (x86_64, ARM64)
Rocky Linux 8 (x86_64, ARM64)
Rocky Linux 9 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, ARM64)
Ubuntu 22.04 (x86_64, ARM64)
Red Hat Enterprise Linux 9 (x86_64, ARM64)
Rocky Linux 8 (x86_64, ARM64)
Rocky Linux 9 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, ARM64)
Ubuntu 22.04 (x86_64, ARM64)
Red Hat Enterprise Linux 9 (x86_64, ARM64)
Rocky Linux 8 (x86_64, ARM64)
Rocky Linux 9 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, ARM64)
Ubuntu 22.04 (x86_64, ARM64)
Ubuntu 20.04 (x86_64)
Ubuntu 20.04 (x86_64)
Red Hat Enterprise Linux 8
SUSE Linux Enterprise Server 12
SUSE Linux Enterprise Server 15
Ubuntu 18.04
Ubuntu 20.04
In alignment with the enterprise lifecycle, MariaDB Enterprise ColumnStore 23.02.9 is provided for:
Debian 11 (x86_64, ARM64)
Red Hat Enterprise Linux 8 (x86_64, ARM64)
Red Hat Enterprise Linux 9 (x86_64, ARM64)
Rocky Linux 8 (x86_64, ARM64)
Rocky Linux 9 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, ARM64)
Ubuntu 22.04 (x86_64, ARM64)
Upgrade Multi-Node MariaDB Enterprise ColumnStore from 6 to 23.10
Continuous workload triggers unknown primitive cmd message in PP log (MCOL-5637)
In alignment with the enterprise lifecycle, MariaDB Enterprise ColumnStore 23.02.8 is provided for:
Debian 11 (x86_64, ARM64)
Red Hat Enterprise Linux 8 (x86_64, ARM64)
Red Hat Enterprise Linux 9 (x86_64, ARM64)
Rocky Linux 8 (x86_64, ARM64)
Rocky Linux 9 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, ARM64)
Ubuntu 22.04 (x86_64, ARM64)
Upgrade Multi-Node MariaDB Enterprise ColumnStore from 6 to 23.10
In alignment with the enterprise lifecycle, MariaDB Enterprise ColumnStore 23.02.3 is provided for:
Debian 11 (x86_64, ARM64)
Red Hat Enterprise Linux 8 (x86_64, ARM64)
Red Hat Enterprise Linux 9 (x86_64, ARM64)
Rocky Linux 8 (x86_64, ARM64)
Rocky Linux 9 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, ARM64)
Ubuntu 22.04 (x86_64, ARM64)
Upgrade Multi-Node MariaDB Enterprise ColumnStore from 6 to 23.10
An error can be returned during disk aggregation. (MCOL-5213)
The following error message could be raised to the client:
An issue related to manual package upgrade was identified in RPM packages. (MCOL-5218)
In alignment with the enterprise lifecycle, MariaDB Enterprise ColumnStore 22.08.2 is provided for:
CentOS 7 (x86_64)
Debian 10 (x86_64, ARM64)
Debian 11 (x86_64, ARM64)
Red Hat Enterprise Linux 7 (x86_64)
Red Hat Enterprise Linux 8 (x86_64, ARM64)
Red Hat Enterprise Linux 9 (x86_64, ARM64)
Rocky Linux 8 (x86_64, ARM64)
Rocky Linux 9 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, ARM64)
Ubuntu 22.04 (x86_64, ARM64)
Upgrade Multi-Node MariaDB Enterprise ColumnStore from 6 to 23.10
The auto_failover option can be set to True or False in the [application] section:
The default value of the auto_failover option is True.
The auto_failover option should be set to False when is used.
The format and logic of CMAPI logging has been improved. (MCOL-4907)
Transaction IDs are included more consistently in exception messages. ()
In alignment to the MariaDB Corporation Engineering Policy, CMAPI 6.4.1 is provided for:
CentOS 7 (x86_64)
Debian 10 (x86_64)
Red Hat Enterprise Linux 7 (x86_64)
Red Hat Enterprise Linux 8 (x86_64)
Rocky Linux 8 (x86_64)
Ubuntu 18.04 (x86_64)
Ubuntu 20.04 (x86_64)
This page is: Copyright © 2025 MariaDB. All rights reserved.
To avoid conflicts between systemd and CMAPI, the mariadb-columnstore systemd unit is disabled when CMAPI is installed and re-enabled when CMAPI is uninstalled. (MCOL-4938)
Some CMAPI Log messages have been clarified. (MCOL-4851)
CMAPI properly applies configuration changes to multiple nodes. (MCOL-4851)
Behavior for DBRM socket send and receive has been fixed. (MCOL-4851)
The CMAPI configuration file is now automatically created by default if it is not found. (MCOL-4851)
In alignment with the MariaDB Corporation Engineering Policy, CMAPI 1.6.0 is provided for:
CentOS 7 (x86_64)
Debian 9 (x86_64)
Debian 10 (x86_64)
Red Hat Enterprise Linux 7 (x86_64)
Red Hat Enterprise Linux 8 (x86_64)
SUSE Linux Enterprise Server 12 (x86_64)
SUSE Linux Enterprise Server 15 (x86_64)
Ubuntu 18.04 (x86_64)
Ubuntu 20.04 (x86_64)
This page is: Copyright © 2025 MariaDB. All rights reserved.
ColumnStore now includes Cluster Management API (CMAPI) 6.4.1.
ColumnStore has optimized the storage and usage of the Extent Map to improve scalability. (MCOL-4917)
The Extent Map is now stored as a red-black tree instead of a linear array.
The Extent Map's new data structure provides optimizations for many operations.
The mcsRebuildEM utility now supports both the ColumnStore Object Storage Topology and the ColumnStore Shared Local Storage Topology. ()
The mcsRebuildEM utility now calculates the high water mark for system catalog files. ()
ColumnStore's systemd unit files use startup and shutdown timeouts that are too low, which can lead to race conditions during startup and shutdown. (MCOL-4775, MCOL-4867, MCOL-5105)
The race conditions could cause the Extent Map to become corrupt.
The race conditions could also cause the DMLProc process to repeatedly try to rollback the same transactions in a crash loop.
When a recursive CTE is executed with a ColumnStore table, the server crashes. ()
Starting with this release, when a recursive CTE is executed with a ColumnStore table, the ER_CHECK_NOT_IMPLEMENTED error code is raised to the client with the following message:
<.
ERROR 1178 (42000): The storage engine for the table doesn't support Recursive CTE
<>
When a disk-based JOIN is executed, ExeMgr can crash. ()
Internal installation scripts refer to legacy OAM components and can break some installations. (MCOL-5060)
In alignment with the enterprise lifecycle, MariaDB Enterprise ColumnStore 6.4.1 is provided for:
CentOS 7 (x86_64)
Debian 10 (x86_64)
Red Hat Enterprise Linux 7 (x86_64)
Red Hat Enterprise Linux 8 (x86_64)
Rocky Linux 8 (x86_64)
Ubuntu 18.04 (x86_64)
Ubuntu 20.04 (x86_64)
This page is: Copyright © 2025 MariaDB. All rights reserved.
CMAPI 1.6.2 was originally included
CMAPI 1.6.3 is now included
CMAPI is a REST API for administering MariaDB Enterprise ColumnStore in multi-node topologies.
For additional information, see "Release Notes for CMAPI 1.6.2" and "Release Notes for CMAPI 1.6.3".
Related to performance
When performing a bulk data load, performance can be negatively impacted by slow extent map lookups. (MCOL-4912)
In alignment with the enterprise lifecycle, MariaDB Enterprise ColumnStore 5.6.5 is provided for:
CentOS 7 (x86_64)
Debian 10 (x86_64)
Red Hat Enterprise Linux 7 (x86_64)
Red Hat Enterprise Linux 8 (x86_64)
Ubuntu 18.04 (x86_64)
Ubuntu 20.04 (x86_64)
Major Release Upgrades for MariaDB Enterprise ColumnStore.
CMAPI 1.6 is now included
CMAPI is a REST API for administering MariaDB Enterprise ColumnStore in multi-node topologies.
For additional information, see "Release Notes for CMAPI 1.6".
ColumnStore now supports compression for temporary files used for disk-based aggregations (MCOL-4829)
When disk-based aggregations are enabled, the temporary files use snappy compression by default.
The CMAPI shell aliases fail when the API key contains a = character. (MCOL-4773)
In alignment with the enterprise lifecycle, MariaDB Enterprise ColumnStore 5.6.3 is provided for:
CentOS 7 (x86_64)
Debian 9 (x86_64)
Debian 10 (x86_64)
Red Hat Enterprise Linux 7 (x86_64)
Red Hat Enterprise Linux 8 (x86_64)
SUSE Linux Enterprise Server 12 (x86_64)
SUSE Linux Enterprise Server 15 (x86_64)
Ubuntu 18.04 (x86_64)
Ubuntu 20.04 (x86_64)
Major Release Upgrades for MariaDB Enterprise ColumnStore.
MariaDB Enterprise ColumnStore 23.10.3 is a maintenance release of MariaDB Enterprise ColumnStore. MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server.
MariaDB Enterprise ColumnStore 23.10.3 was released on 2025-01-27. This release is of General Availability (GA) maturity. MariaDB Enterprise ColumnStore 23.10.3 is a GA release in the 23.10 series.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.6.20-16.
NOT LIKE is not compatible with MariaDB on explicit NULL ()
LEFT(str, negativeInt) returns a wrong result ()
Having not() provokes an ERROR 2013 ()
MariaDB Columnstore produces wrong averages on extracted null-datetime fields (like year) ()
Reading a Columnstore table via a view using "count" crashes when the view has "order by" in definition ()
CMAPI self-signed cert are expired after one year.. which leads to "Connection refused" messages ()
Columnstore crashes/unstable on too large selects ()
OOM occurs during disk based aggregation with um_mem_limit > 0 ()
ByteStreamProcessor is slow with UM JOIN ()
Remove boost::iequals from the code because it takes a global lock getting a locale ()
In alignment with the , MariaDB Enterprise ColumnStore 23.10.3 is provided for:
Debian 11 (x86_64, ARM64)
Debian 12 (x86_64, ARM64)
Red Hat Enterprise Linux 8 (x86_64, ARM64)
Red Hat Enterprise Linux 9 (x86_64, ARM64)
Upgrade Multi-Node MariaDB Enterprise ColumnStore from 6 to 23.10
MariaDB Enterprise ColumnStore 23.10.0 is a feature release of MariaDB Enterprise ColumnStore. MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server.
MariaDB Enterprise ColumnStore 23.10.0 was released on 2023-10-11. This release is of General Availability (GA) maturity. MariaDB Enterprise ColumnStore 23.10.0 is the first GA release in the 23.10 series.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.6.15-10.
The changes listed here are relative to MariaDB Enterprise ColumnStore 23.02.4.
Improved compatibility with InnoDB behavior when performing a WHERE clause with NULL comparison. ()
The default character set and collation have changed.
In previous releases, latin1 is the default character set. latin1 uses 1 byte per character.
Starting with this release, utf8 (utf8mb3) is the default character set. utf8mb3 uses 3 bytes per character.
Some commands have one or multiple optional arguments, to see optional argument values, use the --help argument after any command, for example:
Collation information is available to the cpimport utility through the system catalog. ()
cpimport is character set aware. ()
Improved Disk Join step to handle corner cases for large data. ()
The columnstore.cnf has been cleaned up and updated. Unused code has been deleted. Certain server settings related to ColumnStore performance that may differ than the server's own defaults have been added, for example, character_set_server and collation_server. (
After a DML failure, the table lock remains. ()
After using ALTER TABLE to add a new AUTOINCREMENT column or to change a column to AUTOINCREMENT, callastinsertid() shows incorrect autoincrement value. ()
Trailing spaces behave differently in ColumnStore than in InnoDB causing unexpected results. ()
With a query containing a 3 table JOIN, the wrong result can be returned. ()
columnstore_diskjoin_force_run system variable added
columnstore_diskjoin_max_partition_tree_depth system variable added
columnstore_max_allowed_in_values system variable added
columnstore_max_pm_join_result_count system variable added
character_set_client changed from latin1 to utf8mb3
character_set_connection changed from latin1 to utf8mb3
character_set_database changed from latin1 to utf8mb3
character_set_results changed from latin1 to utf8mb3
If an existing table schema contains column types whose byte width now exceed the maximum byte width for that column type, dropping and creating the table with the new version without specifying CHARSET=latin1, will fail. Users should specify CHARSET=latin1 in CREATE TABLE statements.
In alignment with the , MariaDB Enterprise ColumnStore 23.10.0 is provided for:
CentOS 7 (x86_64)
Debian 11 (x86_64, ARM64)
Debian 12 (x86_64, ARM64)
Red Hat Enterprise Linux 7 (x86_64)
Upgrade Multi-Node MariaDB Enterprise ColumnStore from 6 to 23.10
MariaDB Enterprise ColumnStore 23.02.13 is a maintenance release of MariaDB Enterprise ColumnStore. MariaDB Enterprise ColumnStore is a columnar storage engine that is included with the MariaDB Enterprise Server.
MariaDB Enterprise ColumnStore 23.02.13 was released on 26 Mar 2025. This release is of General Availability (GA) maturity. MariaDB Enterprise ColumnStore 23.02.13 is a GA release in the 23.02 series.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.6.14-9.
Users of earlier MariaDB Enterprise ColumnStore releases are encouraged to upgrade.
Improved memory management across JOIN, DISTINCT and ORDER BY operations to prevent out-of-memory events and related crashes ()
Introduced the mcs-load-brm-from-file utility to assist in manually resolving certain upgrade issues ()
Multiplication between a GROUP BY key and an averaged value can error out ()
Control flow could fail resulting in hung queries ()
In alignment with the , MariaDB Enterprise ColumnStore 23.02.13 is provided for:
Debian 11 (x86_64, ARM64)
Red Hat Enterprise Linux 8 (x86_64, ARM64)
Red Hat Enterprise Linux 9 (x86_64, ARM64)
Rocky Linux 8 (x86_64, ARM64)
Upgrade Multi-Node MariaDB Enterprise ColumnStore from 6 to 23.10
MariaDB Enterprise ColumnStore 23.02.12 is a maintenance release of MariaDB Enterprise ColumnStore. MariaDB Enterprise ColumnStore is a columnar storage engine that is included with the MariaDB Enterprise Server.
MariaDB Enterprise ColumnStore 23.02.12 was released on 2025-03-13. This release is of General Availability (GA) maturity. MariaDB Enterprise ColumnStore 23.02.12 is a GA release in the 23.02 series.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.6.14-9.
Users of earlier MariaDB Enterprise ColumnStore releases are encouraged to upgrade.
Remove boost::iequals from the code b/c it takes a global lock getting a locale ()
RGData ui32 counters limits us with addressing big data ()
Upgrade 23.02.10 -> 23.10.2 Failing @ Customer ()
In alignment with the , MariaDB Enterprise ColumnStore 23.02.12 is provided for:
Debian 11 (x86_64, ARM64)
Red Hat Enterprise Linux 8 (x86_64, ARM64)
Red Hat Enterprise Linux 9 (x86_64, ARM64)
Rocky Linux 8 (x86_64, ARM64)
Upgrade Multi-Node MariaDB Enterprise ColumnStore from 6 to 23.10
MariaDB Enterprise ColumnStore 23.02.10 is a maintenance release of MariaDB Enterprise ColumnStore. MariaDB Enterprise ColumnStore is a columnar storage engine that is included with the MariaDB Enterprise Server.
MariaDB Enterprise ColumnStore 23.02.10 was released on 2024-08-20. This release is of General Availability (GA) maturity. MariaDB Enterprise ColumnStore 23.02.10 is a GA release in the 23.02 series.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.6.14-9.
Users of earlier MariaDB Enterprise ColumnStore releases are encouraged to upgrade.
Remove boost::iequals from the code because it takes a global lock getting a locale ()
SM doesn't quit endless loop when S3 service returns non-retryable error ()
In alignment with the MariaDB Enterprise ColumnStore 23.02.10 is provided for:
Debian 11 (x86_64, ARM64)
Red Hat Enterprise Linux 8 (x86_64, ARM64)
Red Hat Enterprise Linux 9 (x86_64, ARM64)
Rocky Linux 8 (x86_64, ARM64)
Upgrade Multi-Node MariaDB Enterprise ColumnStore from 6 to 23.10
MariaDB Enterprise ColumnStore 23.02.3 is a maintenance release of MariaDB Enterprise ColumnStore. MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server.
MariaDB Enterprise ColumnStore 23.02.3 was released on 2023-05-03. This release is of General Availability (GA) maturity. MariaDB Enterprise ColumnStore 23.02.3 is the third GA release in the 23.02 series.
MariaDB Enterprise ColumnStore 23.02 replaces MariaDB Enterprise ColumnStore 22.08 in MariaDB Enterprise Server 10.6.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.6.12-7.
Users of earlier MariaDB Enterprise ColumnStore releases are encouraged to upgrade.
When the GROUP_CONCAT() function is used to produce relatively long strings, excessive memory can be used, which can cause PrimProc to crash with a segmentation fault. (, )
In previous releases, this issue can cause various types of messages to appear in the ColumnStore logs prior to the crash, such as:
In previous releases, this issue can cause clients to see the following error message:
Starting with this release, less memory should be used in this scenario.
When multiple ColumnStore threads or processes try to access a managed shared memory segment for the Extent Map concurrently, a read/write conflict can cause the processes to crash with a segmentation fault due to a race condition. ()
In previous releases, cpimport, PrimProc, and DMLProc were observed to crash in this scenario.
Starting with this release, the internal RWLock is upgraded to a write lock when a shared memory segment remap is initiated (such as by a long running cpimport job), thus avoiding this read/write conflict.
In alignment with the , MariaDB Enterprise ColumnStore 23.02.3 is provided for:
Debian 11 (x86_64, ARM64)
Red Hat Enterprise Linux 8 (x86_64, ARM64)
Red Hat Enterprise Linux 9 (x86_64, ARM64)
Rocky Linux 8 (x86_64, ARM64)
Upgrade Multi-Node MariaDB Enterprise ColumnStore from 6 to 23.10
MariaDB Enterprise ColumnStore 23.02.1 is a feature release of MariaDB Enterprise ColumnStore. MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server.
MariaDB Enterprise ColumnStore 23.02.1 was released on 2023-03-13. This release is of General Availability (GA) maturity. MariaDB Enterprise ColumnStore 23.02.1 is the first GA release in the 23.02 series.
MariaDB Enterprise ColumnStore 23.02 replaces MariaDB Enterprise ColumnStore 22.08 in MariaDB Enterprise Server 10.6.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.6.12-7.
Users of earlier MariaDB Enterprise ColumnStore releases are encouraged to upgrade.
Support added for loading data from AWS S3 via a UDF columnstore_info.load_from_s3 which allows data loading with cpimport for those with no access to the command line. ()
Allow pushdown of queries involving UNION in outer SELECT to ColumnStore engine. ()
MariaDB Enterprise ColumnStore 23.02.1 is confirmed to be compatible with TPC-H benchmark tests.
Starting with this release, GROUP BY handler is disabled by default. GROUP BY pushdown may produce unexpected results. In prior releases, GROUP BY handler was rarely used because it was last in precedence. (
In alignment with the , MariaDB Enterprise ColumnStore 23.02.1 is provided for:
CentOS 7 (x86_64)
Debian 11 (x86_64, ARM64)
Red Hat Enterprise Linux 7 (x86_64)
Red Hat Enterprise Linux 8 (x86_64, ARM64)
Upgrade Multi-Node MariaDB Enterprise ColumnStore from 6 to 23.10
MariaDB Enterprise ColumnStore 22.08.7 is a maintenance release of MariaDB Enterprise ColumnStore. MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server.
MariaDB Enterprise ColumnStore 22.08.7 was released on 2022-12-21. This release is of General Availability (GA) maturity.
MariaDB Enterprise ColumnStore 22.08 replaces MariaDB Enterprise ColumnStore 6 in MariaDB Enterprise Server 10.6.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.6.11-6.
Users of earlier MariaDB Enterprise ColumnStore 22.08 releases are encouraged to upgrade.
When the ExeMgr facility in the PrimProc process is restarted, if the SELECT component of an UPDATE statement fails, the DMLProc process performs a ROLLBACK operation, which can hang if the ExeMgr facility is not yet available. ()
Starting with this release, if this scenario occurs, DMLProc avoids the hang by retrying the operation after a timeout period.
When ExeMgr is writing to the network, the process can sporadically crash due to a race condition. ()
When the primary node is restarted, CMAPI and MaxScale sometimes choose different nodes to be the primary node. (, )
In previous releases, after the primary node was restarted, CMAPI would continue using the old primary server, but MaxScale would failover to a new primary server. If a user tried to select data from the new primary node, the operation could fail with the following error until the node is restarted:
Additionally, the new primary node could write messages like the following to ColumnStore's debug.log file:
Starting with this release, after the primary node is restarted, both CMAPI and MaxScale should failover to the same primary server.
When a CTE contains a query that joins an table and a table, if the CTE results contain a , the column can sometimes be returned as a zero-date (which is 0000-00-00 00:00:00). ()
When a is NULL and is cast to INT, the conversion would fail, and PrimProc would excessively write log messages to its systemd journal. ()
In previous releases, the systemd journal for PrimProc could contain many messages like the following:
Starting with this release, PrimProc no longer writes those log messages to its systemd journal.
In alignment with the , MariaDB Enterprise ColumnStore 22.08.7 is provided for:
CentOS 7 (x86_64)
Debian 11 (x86_64, ARM64)
Red Hat Enterprise Linux 7 (x86_64)
Red Hat Enterprise Linux 8 (x86_64, ARM64)
Upgrade Multi-Node MariaDB Enterprise ColumnStore from 6 to 23.10
MariaDB Enterprise ColumnStore 6.2.2 is a maintenance release of MariaDB Enterprise ColumnStore . MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server. This is the second release in the Enterprise ColumnStore 6 series.
MariaDB Enterprise ColumnStore 6.2.2 was released on 2021-12-13. This release is of General Availability (GA) maturity.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.6.5-2.
CMAPI 1.6 is now included
CMAPI is a REST API for administering MariaDB Enterprise ColumnStore in multi-node topologies.
For additional information, see "Release Notes for CMAPI 1.6".
Performance improvements for query execution (, )
When columnstore_select_handler=ON is configured, the server can crash if a SELECT statement uses aggregate functions. ()
The ColumnStore storage engine sometimes attempts to connect to the ExeMgr process on the old primary ColumnStore node after failover. ()
cpimport writes output to standard error (stderr) when no error occurs. ()
SELECT and UPDATE statements fail when the statement uses the CONVERT_TZ() function. () The following error message would be raised to the client:
SELECT statements sometimes fail when the statement uses the RAND() function (, )
The following error message would be raised to the client:<<code>>
ERROR 1815 (HY000): Internal error: IDB-2045: At least one PrimProc closed the connection unexpectedly.
<.
SELECT statements could return wrong results on large tables if the WHERE condition contains varchar_col < char_col ()
In alignment with the , MariaDB Enterprise ColumnStore 6.2.2 is provided for:
CentOS 7 (x86_64)
Debian 9 (x86_64)
Debian 10 (x86_64)
Red Hat Enterprise Linux 7 (x86_64)
This page is: Copyright © 2025 MariaDB. All rights reserved.
MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server. This is the third release in the Enterprise ColumnStore 5 series.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.5.8-5.
This release is of General Availability (GA) maturity.
MariaDB Enterprise ColumnStore 5.5.1 was released on 2020-12-14.
Documentation
ColumnStore VARCHAR was sized in bytes, which required customers with multi-byte data to account for the byte variance within their capacity calculations and column definitions. VARCHAR is now sized by characters (which may be multi-byte) in alignment to the behavior of InnoDB and as required by SQL standard (ISO/IEC 9075:2016 feature E021 - Character string types). ()
Non-equality comparison operators previously produced storage engine-specific results with NOPAD collations. This behavior now aligns to the behavior of InnoDB. ()
Added ENCODE() and DECODE() function support. ()
Possible crash in mariadbd when calling stored procedures in the columnstore_info database. ()
INSERT .. SELECT hangs on cpimport when MariaDB Enterprise ColumnStore is installed in a non-default path. ()
Incorrect error message shown when using unsupported JSON functions. ()
Equality does not respect the NOPAD collation attribute. ()
ROUND() function returns incorrect answer for DATE data type. (, )
calgetshowpartitions fails if MariaDB Enterprise Server started before MariaDB Enterprise ColumnStore. ()
mcs-loadbrm and mcs-savebrm have hard coded paths to load_brm and save_brm ()
In-place upgrade from 1.5 to 5.5 failed due to DEB package conflicts. ()
A configuration file x-columnstore.cnf previously existed during Beta and Gamma releases of ColumnStore. This file has been removed as it is no longer required. ()
In alignment with the , MariaDB Enterprise ColumnStore 5.5.1 is provided for:
CentOS 8
CentOS 7
Debian 10
Debian 9
MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server. This is the second release in the Enterprise ColumnStore 5 series.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.5.6-4.
This release is of General Availability (GA) maturity.
MariaDB Enterprise ColumnStore 5.4.3 was released on 2020-11-09.
Documentation
statements crashing the Server. ()
statements not working when selecting from to ColumnStore tables. ()
statements crashing when is set to ON or ALWAYS ()
In alignment with the , MariaDB Enterprise ColumnStore 5.4.3 is provided for:
CentOS 8
CentOS 7
Debian 10
Debian 9
MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server. This is the first release in the Enterprise ColumnStore 6 series.
MariaDB Enterprise ColumnStore 6.1.1 was released on 2021-08-26. This release is of General Availability (GA) maturity.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.6.4-1.
Release date: 29th May 2018
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 release.
For an overview of see
Please provide feedback in 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 or subscribe to mariadb-columnstore@googlegroups.com
MCS-2056: There was an IO error during a disk-based aggregation: No such file or directory
GROUP BY can return duplicates. (MCOL-5213)[application]
auto_failover = FalseColumnStore's ExeMgr process now performs fewer context switches.
ColumnStore's PrimProc process now uses less memory.
Some internal operations have been improved to use more parallelism.
JOIN support for columns using increased DECIMAL precision (MCOL-4173)
ColumnStore can now JOIN tables on DECIMAL(38) columns.
Utility to rebuild the Extent Map (MCOL-312)
The mcsRebuildEM utility is now installed by Enterprise ColumnStore.
Enterprise ColumnStore uses the Extent Map to store metadata about the data stored in each extent. There are certain situations when metadata in the Extent Map can become inconsistent with the extents. In these situations, the Extent Map should be rebuilt.
When no options are provided, the mcsRebuildEM utility rebuilds the Extent Map. It does not check whether the Extent Map is already consistent with the extents. It rebuilds the Extent Map even if the Extent Map is already consistent.
When the -d option is provided, the mcsRebuildEM utility displays what changes it would make to the Extent Map and exits. This option can be used to test the operation without writing changes to disk.
When the -s option is provided, the mcsRebuildEM utility displays the current contents of the Extent Map and exits.
When columnstore_select_handler=ON is configured, SELECT statements returns the wrong results if a predicate in the WHERE condition uses an alias that is dependent on the result of a window function. (MCOL-4719)
The columnstoreAlias.sh script raises an error upon login for single node ColumnStore (MCOL-4832)
SUSE Linux Enterprise Server 12 (x86_64)
SUSE Linux Enterprise Server 15 (x86_64)
Ubuntu 18.04 (x86_64)
Ubuntu 20.04 (x86_64)
ERROR 1178 (42000): The storage engine for the table doesn't support IDB-1001: Function 'convert_tz' isn't supported.select-union-select gives corrupted values (MCOL-5307)
Wrong result ('pNuLl_' instead of NULL) in the TEXT column when LEFT OUTER JOIN is used with WHERE condition (MCOL-5581)
Incorrect columnstore result | implicit self joins (MCOL-5651)
UNION query returns incorrect results when one table is ENGINE COLUMNSTORE (MCOL-5669)
DAY function returns wrong result in query on Columnstore table (MCOL-5670)
Different Resultset with AllowDiskBasedAggregation = Y (MCOL-5691)
UNION/INTERSECT/EXCEPT VALUES crashes the server if a ColumnStore table is involved (MCOL-5703)
Columnstore: SELECT SUM(0) may cause data type unknown error (MCOL-5708)
ALTER Column VARCHAR | Not Supported (MCOL-5779)
MariaDB Columnstore 23.10.2: wrong COUNT DISTINCTs in GROUP BY (MCOL-5875)
SELECT GROUP BY is not picking not-NULL values (MCOL-5755)
SELECT CONCAT() throws error: MCS-2021 (MCOL-5776)
SM doesn't quit endless loop when S3 service returns non-retryable error (MCOL-5785)
MCS crashes when PMSmallSide is raised > 1GB(the current default) (MCOL-5787)
Memory leaks in plugin code (MCOL-5791)
RGData ui32 counters limits us with addressing big data (MCOL-5794)
Separated UM/PM topologies are broken b/c DEC sends request to impossible PM id (MCOL-5805)
UM/PM roles are broken in DEC::writeToClients (MCOL-5808)
Columnstore Server crashes when REGEX is matched to function return value (MCOL-5812)
Pass UBSAN sanity checks (MCOL-5844)
Rocky Linux 9 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, ARM64)
Ubuntu 22.04 (x86_64, ARM64)
Ubuntu 24.04 (x86_64, ARM64)
If an existing table schema contains column types whose byte width now exceed the maximum byte width for that column type, dropping and creating the table with the new version without specifying CHARSET=latin1, will fail. Users who need latin1 character set should specify CHARSET=latin1 when creating tables (CREATE TABLE). For example, create table t1 (a VARCHAR(8000))engine=columnstore; in the new version using utf8mb3 as the default CHARSET will fail, because the maximum allowable character length will be 2666=(8000/3). So if the user wants to use the existing table schema, latin1 should be specified as the CHARSET either at the column-level (for example, create table t1 (a VARCHAR(8000) charset 'latin1')engine=columnstore; or at the table-level in the DDL, for example, create table t1 (a VARCHAR(8000))engine=columnstore default charset=latin1;
mcs cluster commands support ColumnStore cluster management operations. (MCOL-4848)
mcs cluster status - get MCS cluster status
mcs cluster stop - stop MCS cluster
mcs cluster start - start MCS cluster
mcs cluster restart - restart MCS cluster
mcs cluster node add –-node <hostname\IP\FQDN> - add node to MCS cluster. The –-node argument can be used multiple times in one command.
mcs cluster node remove –-node <hostname\IP\FQDN> - remove node from MCS cluster. The –-node argument can be used multiple times in one command.
mcs cluster set mode –-mode - set MCS cluster mode. Accepted values are readonly and readwrite
mcs cluster set api-key –-key <api_key> - set MCS cluster API management key
mcs cluster –-help - outputs help on each command
With queries containing a JOIN, a bad result set can be produced. (MCOL-5522)
After switching JOIN order, the aggregated count on left join result is incorrect. (MCOL-5543)
After installation or service restart, permissions for the /dev/shm directory are incorrect. (MCOL-5535)
mariadbd --columnstore-diskjoin-force-run command-line option added
mariadbd --columnstore-diskjoin-max-partition-tree-depth command-line option added
mariadbd --columnstore-max-allowed-in-values command-line option added
mariadbd --columnstore-max-pm-join-result-count command-line option added
character_set_server changed from latin1 to utf8mb3
collation_connection changed from latin1_swedish_ci to utf8mb3_general_ci
collation_database changed from latin1_swedish_ci to utf8mb3_general_ci
collation_server changed from latin1_swedish_ci to utf8mb3_general_ci
Red Hat Enterprise Linux 9 (x86_64, ARM64)
Rocky Linux 8 (x86_64, ARM64)
Rocky Linux 9 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, ARM64)
Ubuntu 22.04 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, ARM64)
Ubuntu 22.04 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, ARM64)
Ubuntu 22.04 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, ARM64)
Ubuntu 22.04 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, ARM64)
Ubuntu 22.04 (x86_64, ARM64)
UNION ALL with wrapped selects supports GROUP BY clause. (MCOL-4937)
UNION with signed and unsigned integer types is supported. (MCOL-5205)
UNION operations that can overflow the maximum supported DECIMAL precision of 38 digits generate the following error: (MCOL-5215)
Rocky Linux 8 (x86_64, ARM64)
Rocky Linux 9 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, ARM64)
Ubuntu 22.04 (x86_64, ARM64)
Rocky Linux 8 (x86_64, ARM64)
Rocky Linux 9 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, ARM64)
Ubuntu 22.04 (x86_64, ARM64)
Enhanced performance of multi-node ColumnStore startup. (MCOL-4337)
Red Hat Enterprise Linux 7
SUSE Linux Enterprise Server 15
SUSE Linux Enterprise Server 12
Ubuntu 20.04
Ubuntu 18.04
Ubuntu 16.04
Red Hat Enterprise Linux 7
SUSE Linux Enterprise Server 15
SUSE Linux Enterprise Server 12
Ubuntu 20.04
Ubuntu 18.04
Ubuntu 16.04
There are no documented changes to CMAPI in this release.
Disk-based aggregation allows larger aggregated result sets than can fit in memory (MCOL-4709)
Prior to this feature, all aggregation operations were performed in memory.
Disk-based aggregation is enabled through configuration.
Increased DECIMAL precision ()
The maximum precision of DECIMAL (fixed-point numeric data type) is 38.
Prior to this release, the maximum precision of DECIMAL was 18.
The columnstore_decimal_overflow_check system variable allows Enterprise ColumnStore to check for decimal overflows when working with DECIMAL values of precision >= 18. For additional information, see "Enable Decimal Overflow Checks".
Increased DECIMAL precision used by the AVG() and SUM() aggregate functions when aggregating integer data types ()
The AVG() and SUM() aggregate functions have a maximum precision of 38 digits. This enables AVG() and SUM() to work with larger integer values with less risk of overflow.
Prior to this release, the AVG() and SUM() aggregate functions had a maximum precision of 18 digits.
Transactional tables can be updated with data from ColumnStore tables ()
Through enhancement to Cross-Engine JOIN capabilities, UPDATE statements can update transactional tables (such as InnoDB and MyRocks) with data from ColumnStore tables:
Enterprise ColumnStore's mandatory utility user is used for Cross-Engine JOIN. The mandatory utility user requires the UPDATE privilege. Before this release, UPDATE to ColumnStore data from transactional data was supported, however UPDATE to transactional data from ColumnStore data (an operation that requires Cross-Engine JOIN) was unsupported.
LZ4 compression (MCOL-987)
With this release, MariaDB Enterprise ColumnStore supports LZ4 and Snappy compression. Configuration allows the user to choose the best compression algorithm for their data set.
Before this release, Snappy compression was supported.
OFFSET syntax (MCOL-4645)
With this release, SELECT .. OFFSET .. FETCH syntax is available as an alternative to LIMIT .. OFFSET
The syntax is:
*** The following query demonstrates the syntax:**
Encrypted passwords for the mandatory utility user (MCOL-1175)
This release adds the cskeys and cspasswd command-line utilities.
The cskeys command-line utility generates an encryption key file. The encryption key file is stored in the /var/lib/columnstore directory by default.
The cspasswd command-line utility uses the encryption key file generated by cskeys to encrypt the specified password.
Example usage:
Auto-switch mode for the ColumnStore Select Handler (MCOL-4525)
The AUTO value for the columnstore_select_handler system variable enables the auto-switch mode.
As with prior releases, columnstore_select_handler=ON enables the custom select handler and columnstore_select_handler=OFF disables the custom select handler.
When columnstore_select_handler is set to AUTO, MariaDB Enterprise ColumnStore automatically chooses whether to use the custom select handler for each query.
For additional information, see "Configure the Select Handler".
Optimizer statistics store NDV (Number of Distinct Values) for ColumnStore tables ()
Optimizer statistics can be collected for ColumnStore tables by executing the ANALYZE TABLE statement.
ColumnStore uses the optimizer statistics to add support for queries that contain circular inner joins.
In previous releases, ColumnStore would raise the following error when a query containing a circular inner join was executed:
For additional information, see "Optimizer Statistics".
Reduced resource usage for connection configuration (MCOL-4679)
A format change to the Columnstore.xml configuration file has reduced resource overhead. Connection definitions (PMSn sections) have been simplified.
No manual action is required to change over to the new format. This configuration is handled by CMAPI.
In alignment with the enterprise lifecycle, MariaDB Enterprise ColumnStore 6.1.1 is provided for:
CentOS 7
CentOS 8
Debian 9
Debian 10
Red Hat Enterprise Linux 7
Red Hat Enterprise Linux 8
SUSE Linux Enterprise Server 12
SUSE Linux Enterprise Server 15
Ubuntu 18.04
Ubuntu 20.04
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
empty string values are treated as NULL. This means you cannot insert empty values into a NOT NULL string column.
: 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.
: 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.
: 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.
: 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 .
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
MariaDB Enterprise ColumnStore 23.02.4 is a maintenance release of MariaDB Enterprise ColumnStore. MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server.
MariaDB Enterprise ColumnStore 23.02.4 was released on 2023-07-03. This release is of General Availability (GA) maturity. MariaDB Enterprise ColumnStore 23.02.4 is the fourth GA release in the 23.02 series.
MariaDB Enterprise ColumnStore 23.02 replaces MariaDB Enterprise ColumnStore 22.08 in MariaDB Enterprise Server 10.6.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.6.14-9.
Users of earlier MariaDB Enterprise ColumnStore releases are encouraged to upgrade.
When deploying the ColumnStore Object Storage topology, Cohesity S3 is supported as a hardware storage option by the ColumnStore S3 Storage Manager. ()
The cgroup v2 API is now supported, and values from the cgroup v1 API hierarchy are now validated. ()
When exporting data from a ColumnStore table using SELECT .. INTO OUTFILE or adding data to a ColumnStore table from another ColumnStore table using INSERT .. SELECT, if the size of the ColumnStore table exceeds the amount of RAM on the server, the PrimProc process uses all of the available memory, which cause the out-of-memory (OOM) killer to kill the process and results in the following error: ()
When the JSON_ARRAYAGG() function is used to produce long strings, excessive memory can be used, which can cause PrimProc to crash with a segmentation fault. ()
In previous releases, this issue can cause various types of messages to appear in the ColumnStore logs prior to the crash, such as:
In previous releases, this issue can cause clients to see the following error message:
Starting with this release, less memory should be used in this scenario.
When a node communicates with itself over memory, the node effectively has an unlimited message queue, which causes memory usage to increase until the out-of-memory (OOM) killer kills the process. ()
In previous releases, when a node communicated with itself over memory, the FlowControl mechanism was effectively disabled. Without FlowControl, if a slow consumer exists somewhere in the query execution pipeline, the Distributed Engine Communication (DEC) receive queue can be overloaded.
Starting with this release, FlowControl is enabled when a node communicates with itself over memory.
The EXTRACT(QUARTER FROM <date_value>) function can return an incorrect quarter value. (, )
When executing a query that contains multiple nested SELECT statements that involve a UNION in the inner SELECT statements, an error is returned when columns with the same name are referenced by alias. ()
In previous releases, an error is raised similar to:
When columnstore_use_import_for_batchinsert is enabled, the LOAD DATA INFILE statement loads values incorrectly for the MEDIUMINT, TIME, and TIMESTAMP data types. ()
When using the columnstore_info.load_from_s3 stored procedure, even if the data is successfully loaded to the ColumnStore table, the procedure reports an import failure: ()
When using the columnstore_info.load_from_s3 stored procedure, if cpimport fails, the user connection hangs until the connection times out without any error messages. ()
Starting with this release, the following error message is raised:
When performing a join with a large table, the post-join filters are not applied. ()
In previous releases, this could cause results to be incorrect.
In alignment with the , MariaDB Enterprise ColumnStore 23.02.4 is provided for:
Debian 11 (x86_64, ARM64)
Red Hat Enterprise Linux 8 (x86_64, ARM64)
Red Hat Enterprise Linux 9 (x86_64, ARM64)
Rocky Linux 8 (x86_64, ARM64)
Upgrade Multi-Node MariaDB Enterprise ColumnStore from 6 to 23.10
MariaDB Enterprise ColumnStore 22.08.1 is a maintenance release of MariaDB Enterprise ColumnStore . MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server. This is the first release in the Enterprise ColumnStore 22.08 series.
MariaDB Enterprise ColumnStore 22.08.1 was released on 2022-09-12. This release is of General Availability (GA) maturity.
MariaDB Enterprise ColumnStore 22.08 replaces MariaDB Enterprise ColumnStore 6 in MariaDB Enterprise Server 10.6.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.6.9-5.
This release has been withdrawn. Users of MariaDB Enterprise ColumnStore 22.08.1 should upgrade to MariaDB Enterprise ColumnStore 22.08.3.
Support has been added for JOINs with an ON clause that reference tables that are not involved in the join. ()
Support has been added for circular outer JOINs. ()
Support has been added for complex JOINs in views. (, )
Support has been added for combining outer JOINs and IS NULL filters. ()
In single-node ColumnStore, query performance has been improved by removing a network hop. ()
Performance has been enhanced for queries that filter on numbers. (, )
Performance has been enhanced for DELETE queries. ()
Support for CHAR and VARCHAR have been added for the MODA() function. ()
Distributed implementations of most JSON functions have been added to ColumnStore. ()
This feature does not include JSON_ARRAYAGG, JSON_OBJECTAGG, or JSON_TABLE.
ColumnStore's functions that use the cal prefix have been changed to use the mcs prefix. (
ColumnStore now includes Cluster Management API (CMAPI) 22.08.1.
Some internal improvements have been made to the mcsRebuildEM utility. ()
Operating system compatibility has changed, as designated in MariaDB Engineering Policy, including:
Support for Debian 11, Red Hat Enterprise Linux 9, Rocky Linux 9, and Ubuntu 22.04 have been added.
Support for Debian 9, Debian 10, and Ubuntu 18.04 have been removed.
When ColumnStore is installed and started, ColumnStore's binaries check the system's CPU to confirm that the CPU supports the SIMD instructions required by ColumnStore. ()
On x86_64, ColumnStore requires SSE4.2.
On ARM64, ColumnStore requires NEON.
If the ColumnStore installation scripts determine that the required SIMD instructions are not supported, the following error is raised:
If the ColumnStore binaries are started and determine that the required SIMD instructions are not supported, the following error is raised:
Internal stability improvements have been made to the processes that write data. ()
The WriteEngineServer, DMLProc, and DDLProc processes have been improved.
PrimProc thread pool has been changed to use a fair scheduler. ()
The ExeMgr process has been merged with the PrimProc process. (,
In alignment with the , MariaDB Enterprise ColumnStore 22.08.1 is provided for:
CentOS 7 (x86_64)
Debian 11 (x86_64, ARM64)
Red Hat Enterprise Linux 7 (x86_64)
Red Hat Enterprise Linux 8 (x86_64, ARM64)
Upgrade Multi-Node MariaDB Enterprise ColumnStore from 6 to 23.10
MariaDB Enterprise ColumnStore is a columnar storage engine that is included with the MariaDB Enterprise Server. This is the fourth release in the 5 series.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.5.9-6.
This release is of General Availability (GA) maturity.
MariaDB Enterprise ColumnStore 5.5.2 was released on 2021-03-15.
Added the ec2_iam_mode=enabled option to storagemanager.cnf, which enables an EC2 instance to authenticate with S3 using its IAM role. ()
Added support for CREATE TABLE AS SELECT .. COUNT() .. FROM .. GROUP BY .. ()
Removed legacy OAM scripts. ()
Consolidated ColumnStore log files in the /var/log/mariadb/columnstore/ directory. ()
Extent map can become corrupted during startup under 5.5.1 with a large extent map and shared storage. ()
A join with different collations crashes the ExeMgr process. ()
A time zone conversion results in a hang due to a deadlock in the thread pool. ()
When replication is used, INSERT INTO .. SELECT .. FROM ... results in a hang in the SQL thread. ()
Error message from LOAD DATA INFILE statement mentions wrong path for .err and .bad files. ()
Table remains locked when ColumnStore is forced to restart. ()
CREATE TABLE AS SELECT .. LIMIT 0 writes a row to the table. ()
SELECT DISTINCT col FROM TABLE LIMIT offset, limit statement ignores offset. ()
Configuration files not moved back into place after in-place upgrade. ()
In alignment with the , MariaDB Enterprise ColumnStore 5.5.2 is provided for:
CentOS 8
CentOS 7
Debian 10
Debian 9
Release date: 13th February 2018
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 release.
For an overview of see
Please provide feedback in 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 or subscribe to mariadb-columnstore@googlegroups.com
Release date: 11th May 2017
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 release.
For an overview of see
Please provide feedback in 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 or subscribe to mariadb-columnstore@googlegroups.com
Release date: 17th August 2018
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 release.
For an overview of see
Please provide feedback in 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 or subscribe to mariadb-columnstore@googlegroups.com
Release date: 9th February 2018
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 release.
For an overview of see
Please provide feedback in 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 or subscribe to mariadb-columnstore@googlegroups.com
mcs cluster node remove --helpCAL0005: ThreadPool: Caught exception during execution: boost::thread_resource_error: Resource temporarily unavailable [generic:11]
CAL0000: TupleAggregateStep::doThreadedAggregate() caught std::bad_alloc %%10%%ERROR 1815 (HY000): Internal error: InetStreamSocket::readToMagic: Remote is closedERROR 1178 (42000): The storage engine for the table doesn't support MCS-2060: Union operation exceeds maximum DECIMAL precision of 38ERROR 1815 (HY000): Internal error: DBRM is not responding. Cannot accept queriesNODE_NAME controllernode[409]: 58.561877 |0|0|0| E 29 CAL0000: DBRM: error: SessionManager::getSystemState() failed (network) %%10%%
NODE_NAME messagequeue[409]: 59.588469 |0|0|0| E 31 CAL0000: messageqcpp::hostnameResolver Name or service not known %%10%%
NODE_NAME messagequeue[409]: 01.642554 |0|0|0| E 31 CAL0000: messageqcpp::hostnameResolver Name or service not known %%10%%error in int conversion from ''UPDATE innodb_tab i
JOIN columnstore_tab c
ON i.col1 = c.col1
SET i.col2 = c.col2;OFFSET start { ROW | ROWS }
FETCH { FIRST | NEXT } [ count ] { ROW | ROWS } ONLYSELECT username, purchase
FROM user_purchases
ORDER BY username, purchase
OFFSET 0 ROWS
FETCH NEXT 10 ROWS ONLY;$ cskeys
$ cspasswd '<plain_text_passwd>'
$ mcsSetConfig CrossEngineSupport Password '<encrypted_passwd>'ERROR 1815 (HY000): Internal error: IDB-1003: Circular joins are not supported.Ubuntu 20.04 (x86_64, ARM64)
Ubuntu 22.04 (x86_64, ARM64)
Rocky Linux 8 (x86_64, ARM64)
Rocky Linux 9 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, ARM64)
Ubuntu 22.04 (x86_64, ARM64)
Moved CMAPI log files to the /var/log/mariadb/columnstore/cmapi/ directory. (MCOL-4494)
Added more logs to /etc/logrotate.d/columnstore configuration. (MCOL-4319)
Refactor ColumnStore systemd services to ensure startup waits for network connectivity. (MCOL-4170)
Results from SELECT .. ORDER BY BINARY(col) now match InnoDB. (MCOL-4454)
Results from FLOOR() function now match InnoDB for DATETIME, TIMESTAMP, and TIME columns. (MCOL-4263)
Results from a query with both a left join and an inner join are incorrect. (MCOL-4493)
Performance regression for queries that filter on small CHAR columns that use latin1 character set. (MCOL-4527)
Queries on big tables that filter on small CHAR columns ignore the collation. (MCOL-4539)
Results from a UDAF are incorrect when executed in a non-distributed manner. (MCOL-4585)
Red Hat Enterprise Linux 7
SUSE Linux Enterprise Server 15
SUSE Linux Enterprise Server 12
Ubuntu 20.04
Ubuntu 18.04
Ubuntu 16.04
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
- Bug verification for for 1.1.7 and 1.0.16
- Merge into server tree
- 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
empty string values are treated as NULL. This means you cannot insert empty values into a NOT NULL string column.
: 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.
: 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.
: 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.
: 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 .
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
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
- Debugging symbols are missing
- Error in LIKE behaviour
- Support NULL safe equals (<=>)
- Crash on prepared statement when no parameters bound
- ADDDATE & DATE_FORMAT combo breaks datetime
- Segmentation Fault with non-string SP parameter
- Using BETWEEN together with date functions in WHERE clause 100x slower than InfiniDB
- Merge 10.1.23 into 1.0.9
- 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
empty string values are treated as NULL. This means you cannot insert empty values into a NOT NULL string column.
: 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.
: 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.
: 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 .
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 .
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
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
empty string values are treated as NULL. This means you cannot insert empty values into a NOT NULL string column.
: 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.
: 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.
: 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.
: 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 .
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
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.
- 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
empty string values are treated as NULL. This means you cannot insert empty values into a NOT NULL string column.
: 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.
: 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.
: 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.
: 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 .
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
MariaDB Enterprise ColumnStore 22.08.8 is a maintenance release of MariaDB Enterprise ColumnStore. MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server.
MariaDB Enterprise ColumnStore 22.08.8 was released on 2023-02-10. This release is of General Availability (GA) maturity.
MariaDB Enterprise ColumnStore 22.08 replaces MariaDB Enterprise ColumnStore 6 in MariaDB Enterprise Server 10.6.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.6.11-6.
Users of earlier MariaDB Enterprise ColumnStore 22.08 releases are encouraged to upgrade.
The JSON_ARRAYAGG function is supported for ColumnStore tables as a distributed aggregate function and can be used to aggregate a column's values into a JSON array. (, )
In previous releases, the following error can be raised when the JSON_ARRAYAGG function is called in a query on a ColumnStore table and the ColumnStore select handler is enabled:
Starting with this release, the JSON_ARRAYAGG function can be called in a query on a ColumnStore table when the ColumnStore select handler is enabled. The function accepts a column or expression as an argument. The expression is evaluated for every column in the result set, and all of the values are aggregated into a single JSON array:
In many cases, when a query uses the GROUP_CONCAT function, the query can be converted to use the JSON_ARRAYAGG function instead. The primary benefit is that the JSON_ARRAYAGG function returns a JSON array, and there are many functions and external tools available for reading and manipulating JSON.
Collection of histogram statistics is supported on ColumnStore tables and can be used for cost-based optimization of joins. ()
In previous releases, queries containing complex joins on ColumnStore tables can fail with the following error:
Starting with this release, when histogram statistics are available for a ColumnStore table, the storage engine can use the histogram statistics to determine the uniqueness of a column and process the join graph more efficiently. To collect histogram statistics on a ColumnStore table, use the ANALYZE TABLE statement:
When ColumnStore is configured to use S3-compatible storage, if the endpoint and region parameters in /etc/columnstore/storagemanager.cnf do not refer to the same region where bucket is located, ColumnStore fails to send data to cloud storage, but does not detect the failure. ()
In previous releases, the endpoint would send ColumnStore an HTTP 301 status code to indicate a failure, but ColumnStore would incorrectly treat it as a success.
Starting with this release, ColumnStore correctly identifies the failure and raises an error message:
When processing a hash join, ExeMgr can crash with a SIGABRT. ()
When a SELECT statement calls SUM(COLUMN=VALUE), the statement fails with an unclear error message. ()
In previous releases, the following error is raised:
Starting with this release, the following error is raised:
&#xNAN;<.
ERROR 1178 (42000): The storage engine for the table doesn't support MCS-2027: Non supported item in aggregate function SUM(COLUMN=VALUE).
<.
When the ANALYZE statement is executed with a SQL statement as an argument, ColumnStore can return an error. ()
In previous releases, the following error is sometimes raised:
Starting with this release, an error should not be raised, and the execution plan should be printed:
When a column is added to a table on a primary node with multi-node ColumnStore, ColumnStore tries to add the new column to the table twice on the replica nodes, which causes a replication failure. ()
In previous releases, when replication failed, messages like the following appear in the MariaDB error log:<<ocde>>
[ERROR] Slave SQL: Error 'Got error 1815 "Unknown error 1815" from storage engine ColumnStore' on query. Default database: 'db1'. Query: 'ALTER TABLE t1 ADD COLUMN (col2 varchar(100))', Gtid GTID_POS, Internal MariaDB error code: 1030
[Warning] Slave: Got error 1815 "Unknown error 1815" from storage engine ColumnStore Error_code: 1030
[ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'LOG_FILE' position LOG_POS; GTID position 'GTID_POS'
<>
Starting with this release, the query can be executed without raising an error.
When the TRUNCATE() function is called with a CHAR or VARCHAR column that contains numeric characters, an incorrect value is returned. ()
When multi-node ColumnStore is configured to use shared local storage, replica nodes can overwrite their local copies of the extent map files multiple times during shutdown. ()
When columnstore_use_import_for_batchinsert=ON is set on multi-node ColumnStore, INSERT INTO .. SELECT statements in a transaction report that rows were inserted, even though no rows are inserted. ()
In alignment with the , MariaDB Enterprise ColumnStore 22.08.8 is provided for:
CentOS 7 (x86_64)
Debian 11 (x86_64, ARM64)
Red Hat Enterprise Linux 7 (x86_64)
Red Hat Enterprise Linux 8 (x86_64, ARM64)
Upgrade Multi-Node MariaDB Enterprise ColumnStore from 6 to 23.10
MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise ColumnStore. This is the fifth release in the Enterprise ColumnStore 5 series.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.5.10-7.
This release is of General Availability (GA) maturity.
MariaDB Enterprise ColumnStore 5.6.1 was released on 2021-06-14.
LOOR() now returns a fully-formatted DATETIME in alignment to CEIL() behavior. ()
MariaDB Enterprise ColumnStore now supports disk-based aggregation. Prior to this release, all aggregation could occur only in memory. With disk-based aggregation, larger aggregated result sets can be handled than would fit in memory. ()
To enable disk-based aggregation, edit Columnstore.xmland within the RowAggregation section configure:
AllowDiskBasedAggregation=Y to enable the feature. The default is N
To disable SSL certificate verification, edit storagemanager.cnf and configure:ssl_verify = disabled to disable SSL certificate verification. The default is ssl_verify = enabled, which enables SSL certificate verification when connecting by HTTPS to S3-compatible storage.
HTTP connections can now be made to S3-compatible storage. We recommend using HTTPS connections, and to use HTTP connections only when necessary and where appropriate compensatory controls exist. ()
To enable HTTP connections, edit storagemanager.cnf and configure:use_http = enabled to enable HTTP connections to S3-compatible storage. The default is use_http = disabled, which uses HTTPS connections to S3-compatible storage.
TCP port number for S3-compatible storage connections can now be specified by setting port_number in storagemanager.cnf ()
CMAPI now pushes storagemanager.cnf changes to newly-added nodes. Prior to this release, storagemanager.cnf to nodes before they were added. ()
Performance enhancements for general query execution, LIKE, and for subqueries containing a UNION (, , )
New:
Update to CMAPI REST API for node removal:
Old:
New:
CMAPI shutdown of cluster is abrupt, and may occur in the middle of transaction execution or rollback. ()
Crash with JOIN when using certain collations. ()
Crash or performance impact due to SELECT bypassing select handler when @variables are involved in the query projection list. ()
Assert in COUNT(DISTINCT) in a JOIN on Ubuntu 20.04. ()
Assert when a function is used in an aggregation on Ubuntu 20.04. ()
Incorrect result from UNION of a huge narrow DECIMAL (such as 17,1) and BIGINT ()
UDAF can return a bad value instead of expected value NULL ()
DISTINCT is case sensitive even when using case insensitive collation. ()
WHERE is not collation aware on CHAR(1) and CHAR(2) ()
.DEB packages missing /usr/bin/testS3Connection ()
In alignment with the , MariaDB Enterprise ColumnStore 5.5.2 is provided for:
CentOS 7
CentOS 8
Debian 9
Debian 10
Major Release Upgrades for MariaDB Enterprise ColumnStore.
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
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
- ColumnStore has been updated to MariaDB server 10.1.22. This results in some os package dependency changes:
'snappy' library added.
- The auth_gssapi plugin is now bundled with ColumnStore enabling kerberos based authentication. auth_gssapi plugin missing from columnstore package distribution
- The auth_pam plugin is now bundled with ColumnStore enabling LDAP based authentication.
- table_usage() has a calculation error
- enforce limitation of postCfg needing to be run on pm1
- auth_gssapi plugin missing from columnstore package distribution
- auth_pam plugin missing from columnstore
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.
: 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.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
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 .
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 -
Release date: 23rd July 2019
MariaDB ColumnStore 1.2.5 is a GA release of MariaDB ColumnStore. The MariaDB ColumnStore 1.2 series provides several new features and improvements over the MariaDB ColumnStore 1.1 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.
- Critical regression in the dictionary storage of 1.2.4 fixed.
- Assertion failure when using HAVING with constant values
- Fix up regr functions in regrmysql.cpp so regr_* funtions work correcly for InnoDB tables
- cross engine join with space in column names in on condition cause fatal error
- DATE/TIME type math is broken -- TIMEDIFF, TIMESTAMPDIFF and date math
In addition, all bugs fixed in MariaDB ColumnStore 1.2.4 and earlier are implicitly included in this release.
The following procedure outlines upgrading a 1.1.7 ColumnStore install to 1.2.5:
The following procedure outlines upgrading a 1.2.x ColumnStore install to 1.2.5:
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.
- localquery mode tries to turn on replication and fails.
RPM, Debian, and binary packages are provided for the Linux distributions supported by MariaDB ColumnStore 1.2.5 GA version.
The supported OS for the GA version are CentOS 6, CentOS 7, Debian 8, Debian 9, RedHat 6, RedHat 7, SUSE 12, Ubuntu 16.04 and Ubuntu 18.04.
Packages can be downloaded or can be installed from the .
An Amazon AWS AMI Image is available for this release, please search for AMI name "MariaDB-ColumnStore-1.2.5". 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 -
Tools -
Write Data API -
Release date: 14th November 2018
MariaDB ColumnStore 1.2.1 is an Beta release of MariaDB ColumnStore. This is the first release of the MariaDB ColumnStore 1.2 series. The MariaDB ColumnStore 1.2 series provides several new features and improvements over the MariaDB ColumnStore 1.1 release.
MariaDB ColumnStore 1.2.1 is a Beta release.
Do not use beta releases on production systems!
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.
- Non-root install now does not require sudo for the installation tools
- Amazon AMI support for Instances with ENA drivers
- Adapter can't recognize database schema written with backtick
- PDI CS not work in the Pentaho Sever repository
- Test failing in develop
- UPDATE and DELETE reported incorrect affected row count
In addition, all bugs fixed in MariaDB ColumnStore 1.2.0 and earlier are implicitly included in this release.
The following procedure outlines upgrading a 1.2.0 ColumnStore install to 1.2.1:
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.
- mcimport can show a warning about column sizes during import
- regr_slope() and regr_r2() produce incorrect result when used as window functions
RPM, Debian, and binary packages are provided for the Linux distributions supported by MariaDB ColumnStore 1.2.0 Alpha version.
The supported OS for the Alpha version are CentOS 6, CentOS 7, Debian 8, Debian 9, RedHat 6, RedHat 7, SUSE 12, Ubuntu 16.04 and Ubuntu 18.04.
Packages can be downloaded or can be installed from the .
An Amazon AWS AMI Image is available for this release, please search for AMI name "MariaDB-ColumnStore-1.2.0". 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 -
Tools -
Write Data API -
Release date: 3rd December 2018
MariaDB ColumnStore 1.2.2 is a GA release of MariaDB ColumnStore. The MariaDB ColumnStore 1.2 series provides several new features and improvements over the MariaDB ColumnStore 1.1 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.
- NumBlocksPct and TotalUmMemory can take fixed memory sizes instead of percentages
- mcsapi has been split into separate packages for every programming language
- The kafka package has been renamed
- Query doesn't process certain JOIN types with GROUP BY handler.
- BRM_saves_current should use a relative path
- Suse12 regression failure test023 median::nextValue crashing PrimProc
- GROUP BY handler incorrectly process filters with subquery as IN predicate
In addition, all bugs fixed in MariaDB ColumnStore 1.2.1 and earlier are implicitly included in this release.
The following procedure outlines upgrading a 1.1.6 ColumnStore install to 1.2.2:
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.
- INSERT...SELECT and LOAD DATA INFILE when used in a transaction as well as mcsapi can cause dictionary columns to be badly cached
- resumeDatabaseWrites can cause DML/DDL to go active all on UMs simultaneously
- localquery mode tries to turn on replication and fails.
- Running TRUNCATE on a table that has been upgraded from 1.1 -> 1.2 can cause MariaDB server to crash. As a workaround you can DROP and recreate the table.
RPM, Debian, and binary packages are provided for the Linux distributions supported by MariaDB ColumnStore 1.2.2 GA version.
The supported OS for the GA version are CentOS 6, CentOS 7, Debian 8, Debian 9, RedHat 6, RedHat 7, SUSE 12, Ubuntu 16.04 and Ubuntu 18.04.
Packages can be downloaded or can be installed from the .
An Amazon AWS AMI Image is available for this release, please search for AMI name "MariaDB-ColumnStore-1.2.2". 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 -
Tools -
Write Data API -
MariaDB ColumnStore is a columnar storage engine. This is the first GA release in the ColumnStore 1.4 series. This release contains new features and fixes, compared to MariaDB ColumnStore 1.4.2.
This release of MariaDB ColumnStore is included with MariaDB Enterprise Server 10.4.12-6.
MariaDB ColumnStore 1.4.3 was released on 2020-03-02.
MariaDB ColumnStore 1.4.3 is the first Generally Available (GA) release of the ColumnStore 1.4 release series. ()
Support added for ALTER TABLE ... ENGINE=ColumnStore ()
Support added for CREATE TABLE ... ENGINE=ColumnStore AS SELECT ... ()
Potential data loss with S3 StorageManager when mcsadmin suspendDataWrites returns before S3 sync is complete. ()
Server aborts if Columnstore.xml is missing. (, )
A User Module (UM) join memory overflow can cause session hang and fail to free memory. ()
Improper StorageManager shutdown can result if process is killed by fatal error. ()
Incorrect comparison of padded string vs. non-padded column. ()
Incorrect query validation for complex ORDER BY ()
subquery does not return rows with NULL qualifying column values. ()
GROUP BY
StorageManager may log inconsistently. ()
with DISTINCT and two columns may fail. ()
If min/max are set, incorrect results may be provided after a cpimport due to incorrect extent elimination. ()
Performance regression in and ()
Slow DDL statement execution after a restart. ()
postConfigure aborted due to missing /tmp/columnstore_tmp_files directory. ()
postConfigure output 'unassigned' alias script name. ()
columnstore-post-install
Performance of some queries, such as those containing UNION, may be worse than on ColumnStore 1.2.x.
and queries currently fall back to a slower execution method.
None.
In alignment to the MariaDB Corporation Engineering Policy, MariaDB ColumnStore 1.4.4 is provided for:
Red Hat Enterprise Linux 8
Red Hat Enterprise Linux 7
CentOS 8
CentOS 7
Note: MariaDB Enterprise ColumnStore 1.4 is no longer supported. If you would like to deploy Enterprise ColumnStore, please use MariaDB Enterprise ColumnStore 5 or later. For installation and upgrade instructions, see "Deploy".
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
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 10.1.17, including the security fix for (MySQL Remote Root Code Execution / Privilege Escalation 0 day).
: A date of 0000-00-00 is now supported and will not be turned into NULL. Previous NULL conversions will remain as NULL
: 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
: Comment parser in breaks some queries
: LDI using cpimport pads char column values with spaces
: DATETIME field doesn't match with MySQL standard
: DDL parser doesn't support space instead of equals in table options
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 .
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
: 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.
: Following three window functions do not return correct value
FIRST_VALUE
LEAD
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
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 -
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
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
- Debian 9 is now a supported platform.
- The base MariaDB server version is now which include several maintenance and security fixes.
- On a 2PM combo stack with query stats enabled, one of the PMs returned an error when queries is executed
- GROUP BY in a cross engine subquery generates bad results
- primproc crashes sometimes in test001 regression test runs during drop table
- support debian 9
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.
: 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.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
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 .
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 -
MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server. This is the first release in the Enterprise ColumnStore 1.5 series, and marks the first major release since integration with MariaDB Enterprise Server.
This release is focused on architectural change, product quality, and improved alignment to MariaDB Enterprise Server.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.5.4-2.
This release is of Gamma maturity, and should not be used with production workloads.
MariaDB Enterprise ColumnStore 1.5.3 was released on 2020-07-16.
is a columnar storage engine included with MariaDB Enterprise Server. This is the first release in the 5 series, which succeeds Enterprise ColumnStore 1.5.3.
This release is focused on architectural change, product quality, and improved alignment to MariaDB Enterprise Server.
This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.5.6-4.
This release is of General Availability (GA) maturity.
5.4.1 was released on 2020-10-20.
Release date: 24th November 2016
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.
Do not use Release Candidate releases on production systems!
For an overview of see
Please provide feedback in 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 or subscribe to mariadb-columnstore@googlegroups.com
ERROR 1815 (HY000): Internal error: MCS-2004: Cannot connect to ExeMgr.CAL0000: InetStreamSocket::readToMagic(): I/O error1: rc-1; poll signal interrupt ( POLLHUP POLLERR ) %%10%%
CAL0001: Table does not exist in ColumnStore.ERROR 1815 (HY000): Internal error: InetStreamSocket::readToMagic: Remote is closedERROR 1815 (HY000): Internal error: MCS-3009: Unknown column '.TABLE_ALIAS.COLUMN_ALIAS'.{"success": false, "inserted": 0, "processed": 0}{"error": "2023-06-19 19:12:27 (13398) ERR : Actual error row count(11) exceeds the max error rows(10) allowed for table DATABASE_NAME.TABLE_NAME [1451]\n"}error: this machine CPU lacks of support for Intel SSE4.2 or ARM Advanced SIMD instructions. Columnstore requires one of this instruction sets, installation abortedUnsupported CPU architecture. ARM Advanced SIMD or x86_64 SSE4.2 required; aborting.When querytstats is enabled, if a query contains a LEFT JOIN and the ON clause contains the LOWER() function, an error is written to the ColumnStore log. (MCOL-5223)
In previous releases, the following error is written to the ColumnStore log:
Rocky Linux 8 (x86_64, ARM64)
Rocky Linux 9 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, ARM64)
Ubuntu 22.04 (x86_64, ARM64)
TempDirto the directory path for storing temporary files. The default is /tmp/columnstore_tmp_files/aggregates
SSL certificate verification can now be disabled for S3-compatible storage. We recommend that SSL certificate verification be disabled only when necessary, and where appropriate compensatory controls exist. (MCOL-3542)
TRIM(), CONCAT(), REPLACE(), ENCODE(), and DECODE()sql_mode=ORACLEUpdate to CMAPI REST API for node add:
Old:
Delay in execution of first query after ColumnStore restart. (MCOL-4071)
Long command strings cause crash of cpimport (MCOL-3394)
Failover hangs with multi-node ColumnStore 5.4 when using S3 storage, requiring an API call to restart cluster. (MCOL-4440)
Crash with concurrent Pentaho ETL and queries. (MCOL-4555)
GROUP and DISTINCT are not collation aware on CHAR(1) (MCOL-4721)
LIKE is not collation-aware. (MCOL-4498)
Performance impacted on nested queries with aggregates. (MCOL-4543)
INSERT .. SELECT * FROM (subselect) throws is not in GROUP BY clause even when it is part of the GROUP BY clause. (MCOL-3890)
ERROR 1815 (HY000): Internal error: IDB-1000 on FROM subquery containing nested JOINs. (MCOL-4680)
INSERT from VIEW generates error IDB-1011: Insert on VIEW is currently not supported. (MCOL-4687)
Red Hat Enterprise Linux 8
SUSE Linux Enterprise Server 12
SUSE Linux Enterprise Server 15
Ubuntu 18.04
Ubuntu 20.04
MCOL-611 - Bulk cpimport has been optimized to reduce execution overhead in determining completion across multiple nodes.
MCOL-640 - Support Google Cloud Environment
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
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 .
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 .
MCOL-3239 - CS incorrectly pushes function filter predicate into a subquery.
MCOL-3304 - Window functions in queries with embedded selects produce bad numbers
MCOL-3314 - Exemgr crash on query happening when we increase 2 variables, MaxOutStandingRequests and RequestSize
MCOL-3353 - Possible memory corruption in execplan
MCOL-3367 - ColumnStore API rpm packages failed to install
MCOL-3373 - Bug in funcexp while throwing an exception
MCOL-3384 - Crash in mxs_adapter
MCOL-3385 - Strings returned by the Avro C API include the null terminator in thestring length
MCOL-3391 - columnstore_upgrade failed from 1.2.2 to 1.2.4 when database including multibyte table name
MCOL-3395 - regression: dictionary de-duplication cache bleeding between columns
MCOL-3399 - Regression in LDI string length handling
MCOL-3404 - tpcds query #98 failed with an internal error
MCOL-3321 - some regr_* function tests need order by to make them deterministic
MCOL-3343 - Window Functions don't work with arithmetic operators or other functions
MCOL-1968 - wrong string comparisation after dataimport and extents
MCOL-1989 - Querying view results in internal error: column is not found in info map
MCOL-3398 - Rebase 1.2 on MariaDB 10.3.16
MaxScale CDC and Kafka Data Adapters - Source Code for data adapters
MCOL-1786 - Handle "true" keyword for numeric data types in cpimport - with thanks to community contributor "tntnatbry"
MCOL-1792 - Timestamp --> Datetime insert: milliseconds are wrongly inserted in CS
MCOL-1799 - test013 regression
MCOL-1811 - Rename mcsimport package name during Windows build
MCOL-1812 - Bulk Write SDK Windows installer uninstallation / alter - wrong execute credentials
MCOL-1813 - Bulk Write SDK's Windows installer doesn't detect Python installations for the current user only
MCOL-1821 - mcsimport not included in tools binary package
MCOL-1823 - Amazon AMI quick installer script - add in default to do distributed install
MCOL-1826 - PrimProc crash in float/double to string conversion
MCOL-1845 - RPM package summary need to be consistent
MCOL-1852 - Spark Exporter uses collect() instead of toLocalIterator() on DataFrames to export and therefore uses too much memory on the Driver
MCOL-1858 - An invalid records indication when loading the table unsing mcsimport
MCOL-520 - true non root install phase 1
MCOL-1158 - Support additional Python3 features using Swig's -py3 flag
MCOL-1642 - Add SQL command that shows Primary Front-End MariaDB ColumnStore Module
MCOL-1671 - Windows mcsapi - add option to install libraries directly into Java
MCOL-1774 - mcsimport - enclose by character support and escape character for enclose by char
MCOL-1816 - mcsapi - support bool data type
MCOL-1817 - Pentaho support bool data type
MCOL-1373 - Add TIME & DATETIME+msec support to mcsapi
MCOL-1593 - Add Windows builder to buildbot for API
MCOL-1744 - Remove unnecessary CentOS 7 mcsapi package dependencies
MCOL-1754 - Change libmysql dependency for Windows api tests to libmariadb
MCOL-1804 - Rebase 1.2 on MariaDB 10.3.10
MCOL-1846 - AMI support for Instances with ENA drivers
MCOL-1860 - cannot insert symbols in column using the mcsimport with escape_character option
MCOL-1654 - Querystats table is broken
MaxScale CDC and Kafka Data Adapters - Source Code for data adapters
MCOL-1718 - Clarify configuration requirements for usage of the -z option
MCOL-1742 - CentOS 7 - data-adapter repository installation broken
MCOL-1777 - regr tests depend on table that doesn't exist yet
MCOL-1778 - WF regression tests need fixing
MCOL-1779 - tablemode test failing in develop
MCOL-1793 - regr_slope() and regr_r2() produce incorrect result when used as window functions
MCOL-1800 - test022 regression
MCOL-1847 - need to be able to specify NumBlocksPct and TotalUmMemory explicitly
MCOL-1855 - ColumnStore table whose name contains $ cannot be renamed
MCOL-1868 - func_concat_ws type
MCOL-1875 - getsystemcpu & related commands always return 0 cpu usage
MCOL-1877 - getactivesqlstatements returns 'file open error'
MCOL-1879 - csv text "true" is mapped to 0 during import but should be parsed to 1
MCOL-1885 - Cross engine / Query stats doesn't show specific query errors
MCOL-1900 - PDI Plugin unresponsive if CS is not available
MCOL-1945 - mxs_adapter throws malloc error
MCOL-1947 - Our aliases break BASH
MCOL-1949 - vTpch10.sql and vTpch21.sql regression
MCOL-1953 - columnstoreClusterTester.sh script fails
MCOL-1959 - mxs_adapter assertion crash on multi table stream
MCOL-1094 - mcsapi should have view/clear table lock features
MCOL-1362 - Add a export function that utilizes (sequential) write from Spark workers
MCOL-1739 - Split mcsapi installation into different packages for C++, Java and Python
MCOL-1740 - mcsimport - depend on mcsapi only
MCOL-1844 - Allow prior/custom changes made to myCnf-include-args.text be added to new myCnf-include-args.text after upgrading
MCOL-1790 - Implement new CASE item type detection
MCOL-1866 - Change logo in mcsapi, PDI and mcsimport
MCOL-1944 - /var/log/mariadb/columnstore ownership set to 777 recursive
MCOL-1952 - Rebase develop 10.3.11
MaxScale CDC and Kafka Data Adapters - Source Code for data adapters
cpimport for S3 storage with multi-PM (multi-performance module). (MCOL-3520)Failure to sync timezone variable between queries can trigger a hang. (MCOL-3776)
Failure in disk space pre-allocation for non-compressed data can trigger a crash in cpimport . (MCOL-3791)
Matched and changed row counts may be zero even if rows are changed (Rows matched: 0 Changed: 0). (MCOL-2239)
Queries containing SPACE() may return error 1178. (MCOL-3473)
WHERE and HAVING conditions skipping may generate spurious warnings. (Failure to start when Server is rebooted without mcsadmin shutdownSystem first. (MCOL-3829)
ORDER BY over negative SEC_TO_TIME() results produce an incorrect order. (MCOL-3598)
Stopping Server with systemd triggers restart by ColumnStore. (MCOL-3718)
Note: 1618 COLLATE is ignored in ColumnStore was not correctly surfaced. (MCOL-3721)
Subqueries with ORDER BY ... LIMIT may produce incorrect result. (MCOL-3747)
Package removal doesn't trigger mcsadmin shutdownSystem (MCOL-3708)
Package purge doesn't remove /var/lib/columnstore (MCOL-3709)
Ubuntu 18.04
Ubuntu 16.04
Debian 10
Debian 9
SUSE Linux Enterprise Server 15
SUSE Linux Enterprise Server 12
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
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.
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
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 .
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 .
Comprehensive rewrite of installation, administration, cluster management, and failover logic. (MCOL-3836)
Simplified installation
Users no longer need to execute columnstore-post-install and postConfigure
It is a plugin for MariaDB Enterprise Server.
It is packaged similar to other MariaDB Enterprise Server plugins.
See Installation for more details.
Simplified administration:
mcsadmin has been removed. Instead, Enterprise ColumnStore 1.5 uses systemd for administration of single-node and multi-node deployments, and it also adds a new REST API for administration of multi-node deployments.
The new systemd service called mariadb-columnstore is used to manage ColumnStore's processes.
The new REST API is used to manage multi-node ColumnStore deployments.
This release was the source for fixes previously backported to ColumnStore 1.4.4.
This release includes correction of regressions present in ColumnStore 1.4.4 vs pre-integration.
Fixes for defects in tiered storage and S3-compatible object storage.
Support for standard MariaDB Enterprise Server collation and character sets. ()
Improved performance for REGR_* functions. ()
mariadbd will abort if Columnstore.xml is missing. (MCOL-3853)
Intermittent crash of cpimport in some complicated workflows. (MCOL-3865)
Exceeding thread limits will cause queries against S3-compatible object storage to hang. (MCOL-3858)
Error was not properly returned when a COMMIT or ROLLBACK failed, triggering an assertion. (MCOL-4124)
mcs-storagemanager attempted startup when not needed. (MCOL-4151)
COUNT(DISTINCT) on more than one column produces an error. (MCOL-3857)
REVERSE() function does not work with non-Latin characters. (MCOL-2221)
Multi-table DROP IF EXISTS generates an error instead of a warning. (MCOL-4164)
UPDATE with SELECT returning nulls may produce wrong answer. ()
rand() calls with the same seed value return different results. ()
Attempt to INSERT a TINYINT with an out-of-range value can generate a spurious error message. ()
A query containing a Common Table Expression (CTE) can return the wrong error message, that a field is not in the GROUP BY clause even if it is. ()
Complex queries using UNION can return the wrong error message, table not found. ()
COUNT(NULL) doesn't work as a window function. ()
The wrong error message is given when a function not supported by ColumnStore is used inside a function that is supported by ColumnStore. ()
microsecond support for from_unixtime
INSERT after a LOAD DATA LOCAL INFILE in a transaction may silently fail. ()
IN clause in WHERE could be evaluated improperly. ()
A spurious "file not found" error message can occur when query, truncate, and cpimport collided. ()
Internal error: IDB-2035 can occur with BIT_OR function in projection and subquery in FROM ()
Multi-byte characters mishandled in DML export to cpimport-1.5. ()
GROUP_CONCAT() with ORDER BY and long doubles may fail. ()
CONV() returned less characters in the resulting string. ()
MODA() produces memory leak. ()
Memory leaks. (, )
EXPLAIN generates error on every other (alternating) execution. ()
Renaming a table causes schema to become out of sync between MariaDB Server catalog and ColumnStore. ()
Incorrect COUNT(*) with a complex view. ()
storagemanager.cnf variable $HOME drew path from user's environment. $HOME now points to the current location of ColumnStore data. (MCOL-4014)
Built-in SQL functions do not work in ColumnStore when sql_mode=ORACLE (MCOL-4044)
None.
In alignment to the MariaDB Corporation Engineering Policy, MariaDB Enterprise ColumnStore 1.5.3 is provided for:
Red Hat Enterprise Linux 8
Red Hat Enterprise Linux 7
CentOS 8
CentOS 7
Ubuntu 20.04
Ubuntu 18.04
Ubuntu 16.04
Debian 10
Debian 9
SUSE Linux Enterprise Server 15
SUSE Linux Enterprise Server 12
Documentation
Multi-node Enterprise ColumnStore 5.4.1 requires MaxScale 2.5.
Multi-node Enterprise ColumnStore 5.4.1 requires shared storage, such as GlusterFS, EFS, and NFS. It also optionally supports S3-compatible storage for data, but it still requires shared storage for metadata.
The CMAPI (Cluster Management API) has been updated. Multi-node Enterprise ColumnStore 5.4.1 uses CMAPI 1.1, which still uses version 0.4.0 of the REST API. (MCOL-3909)
Support for Power BI Direct Query Adapter. (MCOL-3935)
Changed default configuration for memory usage, blocks, and set table names. (MCOL-4252)
Prepared Statements causing Signal 11. (MCOL-4282)
Running COUNT() when the sql_select_limit system variable is set may leave the table badly (MCOL-4278)
New segments files created during bulk insertion with cpimport belong to root (MCOL-4328)
Join operations return errors when using upper-case table names. ()
Permissions issue in /tmp/columnstore_tmp_files ()
RENAME TABLE leaving table unusable. ()
Errors returned when using upper-case database names. ()
Server crashing when running queries where no default schema was provided. ()
Regression in subqueries. ()
CMAPI issues configuring multi-node ColumnStore deployment. ()
Changed default common_prefix_depth for S3 to accommodate new paths. ()
Join operations failing on views. ()
Crash/assertion failure after "RWLock failed to attach to the InfiniDB-shm-00020000 shared mem segment, got Permission denied" ()
SUM() and AVG() functions in subqueries returning 0. ()
CEILING() function returning wrong answer for datetimes. ()
CMAPI Server not gracefully handling first nodes with unresolved names in /etc/hostname ()
Case sensitivity in LOCATE(), INSTR(), and FIND_IN_SET() functions. ()
INSERT() function not inserting. ()
SQL syntax error when uninstalling Columnstore plugin package. ()
Replication of InnoDB into ColumnStore ends in SEGV in plugin. ()
Unclear error message when postConfigure fails to access online S3 storage. ()
Integrate with the cluster management code. ()
Column not found in info map when querying views. ()
Query failures on UPDATE statements to InnoDB tables when WHERE clause includes a sub-query on a ColumnStore table. ()
UPDATE... SET statements not updating when using another table. ()
Multi-node not working after executing stop and start commands. ()
Custom cross-engine join user unable to connect. ()
Hangs when requesting data from ColumnStore extents or files. ()
columnstore-post-install and mariadb-columnstore-start.sh fixed to use absolute paths. ()
Procedures hanging when using ColumnStore tables. ()
CMAPI returning error messages when using custom replication user credentials. ()
CMAP incorrectly sed parsing & character for CMAPI key. ()
Database user access unrestricted by IP addresses. ()
Stored procedures failing for Information Schema tables. ()
columnstore_cache_flush_threshold system variable added
columnstore_cache_inserts system variable added
columnstore_select_handler_in_stored_procedures system variable added
mariadbd --columnstore-cache-flush-threshold command-line option added
command-line option added
command-line option added
In alignment with the enterprise lifecycle, MariaDB Enterprise ColumnStore 5.4.1 is provided for:
CentOS 8
CentOS 7
Debian 10
Debian 9
Red Hat Enterprise Linux 8
Red Hat Enterprise Linux 7
SUSE Linux Enterprise Server 15
SUSE Linux Enterprise Server 12
Ubuntu 20.04
Ubuntu 18.04
Ubuntu 16.04
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 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.
- INSERTIONS are lost, no ERROR reported for out-of-range values in STRICT mode
- DROP DATABASE on a database with all empty tables is not accepted
- update two tables with a subquery fails
- With suspendDatabaseWrite enabled, LDI return an incorrect msg
- During restart, ProcessManager sometimes generates a warning
- drop table if exists creates error if table doesn't exist and schema out of synch
- Support method to report on data set size
- Bad NULL match in view subquery
- can't select date value of 0000-00-00
- substr() on view returns NULL sometimes
- table mode 0 and 2 has bad result
- enableLog / disableLog don't work
- dbrm-worker node continuing issues socket read error log
- 10.1.19 Merge
- postConfigure should show cause of write error.
- releasenum gets messed up when not hard set
- remove the restriction in postConfigure for UM memory at 16G
- 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
empty string values are treated as NULL. This means you cannot insert empty values into a NOT NULL string column.
: 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.
: 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.
: 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 .
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 .
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
MariaDB ColumnStore is a columnar storage engine included with MariaDB Enterprise Server. This release of MariaDB ColumnStore is included with MariaDB Community Server 10.5.4.
MariaDB ColumnStore 1.5.2 was released on 2020-06-24. It is the first release in the MariaDB ColumnStore 1.5 series. This release is of Beta maturity, and should not be used with production workloads.
Comprehensive rewrite of installation and administration logic. ()
Simplified installation:
Users no longer need to execute columnstore-post-install and postConfigure
Support to set up tempfiles.d to prevent the OS from flushing /tmp on reboot. ()
Support for faster replication-slave processing. ()
Implements ISTRUE() function. ()
loadbrm process rewritten in Python (mcs-loadbrm.py). Now requires Python 3 as a dependency.
Fixes not evaluating properly in WHERE clauses. ()
Fixes DNS error MessageQueueClient :: setup (): unknown name or service - ExeMgr = unassigned ()
Fixes FILE001.cdf:No such file or directory error when query, and cpimport collided. ()
In alignment to the MariaDB Corporation Engineering Policy, MariaDB Enterprise ColumnStore 1.5.3 is provided for:
Red Hat Enterprise Linux 8
Red Hat Enterprise Linux 7
CentOS 8
CentOS 7
Note: MariaDB Enterprise ColumnStore 1.5 has been superseded by MariaDB Enterprise ColumnStore 5 in MariaDB Enterprise Server 10.5.
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
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
- generate debian packages: A debian package build is now available for Debian and Ubuntu in addition to the binary install.
- implement redistribution logic : An mcsadmin utility command is provided to support redistribution of partitions. For more details see the article.
- 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.
- generate debian packages
- implement redistribution logic
- utility for finding objects file
- remove the restriction in postConfigure for UM memory at 16G
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.
): 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.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
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 .
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 -
MariaDB Server -
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
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.
- split character import issue
- configxml.sh should be case in-sensitive.
- mycnf config change request
- Unexpected results in cross engine join
The following procedure outlines upgrading a 1.0.11 ColumnStore install to 1.0.12:
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.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
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 .
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 -
Release date: 29th May 2019
This version has been removed from production due to MCOL-3395 having the potential to corrupt databases.
MariaDB ColumnStore 1.2.4 is a GA release of MariaDB ColumnStore. The MariaDB ColumnStore 1.2 series provides several new features and improvements over the MariaDB ColumnStore 1.1 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.
- cpimport performance for dictionary data is up to 2x faster.
- If you are performing a major version upgrade or have in the past there is a new stored procedure called columnstore_info.columnstore_upgrade() should be executed.
- Some compiler warnings need fixing
- Memory leak in WriteEngineServ
- Crash when MySQL aggregate UDF is called against Columnstore table
- SystemConfig / WaitPeriod change lost during upgrade
Additional typo fix contribution by Kabike
In addition, all bugs fixed in MariaDB ColumnStore 1.2.3 and earlier are implicitly included in this release.
The following procedure outlines upgrading a 1.1.7 ColumnStore install to 1.2.4:
The following procedure outlines upgrading a 1.2.x ColumnStore install to 1.2.4:
Multi version upgrades generally will work using the same procedure however we can't test every possible permutation so you should test your specific scenario outside of production first if you wish to try this (and this is good practice regardless).
There are a number bugs and known limitations within this version of MariaDB ColumnStore, the most serious of these are listed below.
- localquery mode tries to turn on replication and fails.
RPM, Debian, and binary packages are provided for the Linux distributions supported by MariaDB ColumnStore 1.2.4 GA version.
The supported OS for the GA version are CentOS 6, CentOS 7, Debian 8, Debian 9, RedHat 6, RedHat 7, SUSE 12, Ubuntu 16.04 and Ubuntu 18.04.
Packages can be downloaded or can be installed from the .
An Amazon AWS AMI Image is available for this release, please search for AMI name "MariaDB-ColumnStore-1.2.4". 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 -
Tools -
Write Data API -
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
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
- MariaDB ColumnStore is now based on MariaDB Server 10.1.25.
- The MariaDB ColumnStore Cluster Tester tool is included in the install. This can be run to validate ColumnStore pre-requisities across servers prior to performing a multi node postConfigure. For further details please see .
- system down and high memory alarm set after install
- mysqld not shutdown by shutdownsystem commands, sometimes
- Argument in alias circumvents /.my.cnf option file
- addModule should not be alowed on single-server installs
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.
: 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.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
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 .
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 -
MariaDB ColumnStore is a columnar storage engine. This is the second GA release in the ColumnStore 1.4 series. This release contains new features and fixes, compared to MariaDB ColumnStore 1.4.3.
This release of MariaDB ColumnStore is included with .
MariaDB ColumnStore 1.4.4 was released on 2020-06-08.
Release date: 21st March 2019
is a GA release of MariaDB ColumnStore. The MariaDB ColumnStore 1.2 series provides several new features and improvements over the MariaDB ColumnStore 1.1 release.
For an overview of see
Please provide feedback in 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 or subscribe to mariadb-columnstore@googlegroups.com
Release date: 21st November 2017
is a GA release of MariaDB ColumnStore. This is the third release of the MariaDB ColumnStore 1.1 series. The MariaDB ColumnStore 1.1 series provides several new features and improvements over the MariaDB ColumnStore 1.0 release.
MariaDB ColumnStore 1.1.2 is a release.
For an overview of see
Please provide feedback in 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 or subscribe to mariadb-columnstore@googlegroups.com
Release date: 23rd January 2017
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 release.
For an overview of see
Please provide feedback in 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 or subscribe to mariadb-columnstore@googlegroups.com
ERROR 1178 (42000): The storage engine for the table doesn't support Non supported aggregate type on the select clauseCREATE TABLE t (a INT, b INT)
ENGINE=ColumnStore;INSERT INTO t VALUES
(1,3), (1,5), (8,2), (5,7),
(5,6), (10,1), (6,4), (3,9),
(3,9), (7,2), (7,5), (2,6),
(9,10), (9,5), (4,8);SELECT a, JSON_ARRAYAGG(b)
FROM t
GROUP BY a;+------+------------------+
| a | JSON_ARRAYAGG(b) |
+------+------------------+
| 1 | [3,5] |
| 2 | [6] |
| 3 | [9,9] |
| 4 | [8] |
| 5 | [7,6] |
| 6 | [4] |
| 7 | [2,5] |
| 8 | [2] |
| 9 | [10,5] |
| 10 | [1] |
+------+------------------+ERROR 1815 (HY000) at line 6: Internal error: IDB-1003: Circular joins are not supported.ANALYZE TABLE t1;S3Storage::putObject(): Bucket location not match provided endpoint:, bucket = BUCKET, endpoint = ENDPOINT.ERROR 1815 (HY000): Internal error: std::bad_typeidERROR 1815 (HY000): Internal error: Unknown errorANALYZE SELECT * FROM t1 WHERE c1 = 1;+------+---------------+-------+------+---------------+------+---------+------+------+--------+----------+------------+-------+
| id | select_type | table | type | possible_keys | key | key_len | ref | rows | r_rows | filtered | r_filtered | Extra |
+------+---------------+-------+------+---------------+------+---------+------+------+--------+----------+------------+-------+
| 1 | PUSHED SELECT | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL |
+------+---------------+-------+------+---------------+------+---------+------+------+--------+----------+------------+-------+1e3afaf1eaef Calpont[135]: 37.906020 |0|0|0| E 00 CAL0000: /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.6.8/storage/columnstore/columnstore/dbcon/joblist/tuplehashjoin.cpp@1095: assertion 'idlsz > 1' failedcurl -X PUT https://127.0.0.1:8640/cmapi/0.4.0/cluster/add-node --header 'Content-Type:application/json' --header 'x-api-key:somekey123' --data '{"timeout":20, "node": "172.31.2.106"}' -kcurl -X PUT https://127.0.0.1:8640/cmapi/0.4.0/cluster/node --header 'Content-Type:application/json' --header 'x-api-key:somekey123' --data '{"timeout":20, "node": "172.31.3.254"}' -k | jq .curl -X PUT https://127.0.0.1:8640/cmapi/0.4.0/cluster/remove-node --header 'Content-Type:application/json' --header 'x-api-key:somekey123' --data '{"timeout":20, "node": "172.31.2.106"}' -kcurl -X DELETE https://127.0.0.1:8640/cmapi/0.4.0/cluster/node --header 'Content-Type:application/json' --header 'x-api-key:somekey123' --data '{"timeout":20, "node": "172.31.11.19"}' -k | jq .ERROR 1178 (42000) at line 1: The storage engine for the table
doesn't support IDB-1001: Function 'space' can only be used in
the outermost select or order by clause and cannot be used in
conjunction with an aggregate function.The new REST API provides an interface for MariaDB MaxScale 2.5 to orchestrate the multi-node Enterprise ColumnStore deployment.
See OAM Replacement for more details.
It is packaged similar to other MariaDB Community Server plugins.
Simplified administration:
mcsadmin has been removed. Instead, ColumnStore 1.5 uses systemd for administration
The new systemd service called mariadb-columnstore is used to manage ColumnStore's processes.
Support for standard MariaDB Community Server collation and character sets. (MCOL-337)
Improved performance for REGR_* functions. (MCOL-3837)
Fixes for defects in tiered storage and S3-compatible object storage.
Creates a systemd unit file for the MariaDB ColumnStore service. (MCOL-3914)
Implements MCSNodeControl package. (MCOL-3920)
Implements REST API server. (MCOL-3921)
Merges 3 MariaDB ColumnStore packages into a single package. (MCOL-3991)
Changing systemlang to an unrecognized string now causes MariaDB ColumnStore to not start up. (MCOL-3420)
Support for ALTER TABLE conversion to MariaDB ColumnStore. (MCOL-3852)
Support for COLLATE in DDL and ORDER BY clauses. (MCOL-3862)
Improvements in failover design. (MCOL-3886)
Fixes truncation during updates causing the Server to assert. (MCOL-3749)
Fixes issue where the same erroneous statement returns a different error other run. (MCOL-3777)
Fixes GROUP BY ordering error: IDB-2021: 'ref_genome' is not in GROUP BY clause (MCOL-3782)
Fixes MariaDB asserts when connection is closed. (MCOL-3812)
Fixes incorrect counts in views. (MCOL-3813)
Fixes issue in UNION operations about table not being in query. (MCOL-3828)
Fixes issue where systemctl cat mariadb.service is not working on all systems. (MCOL-3830)
Optimizes execute() of regr_sxx, regr-sxy, and regr_syy (MCOL-3837)
Fixes Server aborting when Columnstore.xml is missing. (MCOL-3853)
Fixes vTpch22.sql hanging. (MCOL-3858)
Fixes issue where renaming table causes schema to go out of sync. (MCOL-3859)
Fixes errors raised by every other run of the EXPLAIN statement. (MCOL-3860)
Fixes fatalHandler usage. (MCOL-3864)
Fixes intermittent cpimport crashes. (MCOL-3865)
Fixes bug3333.sql mismatch. (MCOL-3894)
Fixes fails in Group_concat in ORDER BY with long double (MCOL-3904)
Fixes error message pointing to wrong function. (MCOL-3924)
Fixes memory leak in XML parser. (MCOL-3934)
Fixes microsecond support for FROM_UNIXTIME() function. (MCOL-3959)
Fixes issue using $HOME in storagemanager.cnf variable. (MCOL-4014)
Fixes mishandling of multi-byte characters in DML export to cpimport-1.5. (MCOL-4017)
Fixes window function issues due to 1.4 returning results where 1.2 returns errors. (MCOL-3856)
Fixes cpimport S3 multi-PM usage. (MCOL-3861)
Ubuntu 18.04
Ubuntu 16.04
Debian 10
Debian 9
SUSE Linux Enterprise Server 15
SUSE Linux Enterprise Server 12
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
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 .
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 .
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
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 .
MCOL-2001 - mscadmin redistributeData parameters are not accepted as suggested by the help information.
MCOL-2035 - Some regr_* tests aren't deterministic so comparisons are iffy. RANK()
MCOL-2061 - MariaDB shows warnings and could crash on DDL after upgrade
MCOL-2089 - High CPU usage and slow performance appears when load data with remote mcsimport
MCOL-2091 - UDAF doesn't work if there are two count(distinct) in projection list
MCOL-2244 - There is no way to identify execution thread that causes bottleneck
MCOL-2267 - Query with SUM() erroring - /rowgroup.h@677: assertion '0' failed
MCOL-2273 - getSystemDisk showing incorrect root usage and reporting incorrect alarm
MCOL-3249 - Probably Kafka DA produces '\0' in the end of TEXT or VARCHAR with width > 7
MCOL-3268 - javamcsapi compatibility test fails
MCOL-3293 - UPDATE performance improvement contribution - Contributed by ABS Global
MCOL-3296 - ctrl+c sometimes leaves DMLProc in bad state
MCOL-3307 - Non-Columnstore Window function causes debug assert
MCOL-3311 - regression test212 logs integer expression expected error
MCOL-3318 - RPM warnings appear when installing ColumnStore's MariaDB Server
MCOL-593 - support columnstore tables as slaves to innodb master tables
MCOL-1254 - Add hidden switch for MariaDB async replication
MCOL-2013 - API .NET support - Alpha - Contributed by Bill Adams
MCOL-2076 - Allow simple replication to ColumnStore
MCOL-2129 - Add a new postConfigure flag to resolve submitted hostnames to correct reverse dns names
MCOL-3267 - Support ORDER BY within UNION subqueries
MCOL-3270 - Improve cpimport ingest speed into Dictionary columns - Contributed by ABS Global
MCOL-2068 - add support for using and defaulting memory based settings to docker image
MCOL-3315 - Rebase on MariaDB 10.3.15
MaxScale CDC and Kafka Data Adapters - Source Code for data adapters
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
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 .
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 .
columnstore_use_import_for_batchinsert system variable option ALWAYS added to use cpimport for LOAD DATA LOCAL INFILE and INSERT .. SELECT regardless of whether the query runs in a transaction. This gives the user the ability to use a faster import method, with the caveat that if a user issues a rollback of the transaction, it will have no effect as the data would have already been committed to actual database files by cpimport. (MCOL-4000)
can modify incorrect data due to incorrect WHERE clause handling. (MCOL-4023)
A hang may occur in load_brm on dbroot1 failover. (MCOL-3945)
may be blocked by improper failover. (MCOL-3999)
Crash may occur when using cpimport () to process data containing multi-byte characters. (MCOL-4005)
Rollback may trigger crash of StorageManager. ()
PM failover and movePmDbrootConfig failure on CentOS 7 with glusterfs. ()
Subqueries with ORDER and LIMIT may produce the wrong answer. (MCOL-3747)
Sub-query with and allows non-aggregates in projection. ()
FILE001.cdf:No such file or directory can occur when query, TRUNCATE and cpimport collide. ()
Internal error: IDB-2035 can occur with BIT_OR function in projection and subquery in FROM ()
Incorrect handling of ORDER BY can occur in some queries. ()
Unexpected syntax errors could be returned from window functions. ()
Format(c1,0) returns only sign, without a digit, on a decimal(1) field. ()
returns NULL instead of expected value. ()
MODA() and REGR_ UDAFs are not properly created. ()
, , , and functions did not exist. ()
regr_ tests returns doubles with higher precision than in ColumnStore 1.2. ()
Window function failures could return results rather than errors. ()
ISTRUE() function did not exist. ()
Alternate behavior for rand() vs ColumnStore 1.2. ()
Wrong error could be returned on every second run of an error-generating query. ()
Internal error: IDB-2021: 'tablename' is not in GROUP BY clause could occur. ()
may complain about table not in query. ()
as a window function does not work correctly with NULL values. ()
SQLYog may encounter an error during ColumnStore cross-engine JOINs. ()
with ORDER BY and long doubles may fail. ()
Error messages may point to the wrong function. ()
Microsecond support for ()
after a LOAD DATA LOCAL INFILE in a transaction may silently fail. ()
Unsupported LIMIT in correlated subqueries may give erroneous result. ()
postConfigure uses invalid device nodes for dbroots. (MCOL-2022)
startsystem allows startup without correct DBROOT 1 assignment. (MCOL-2153)
Incorrect handling of unassigned IP addresses in configuration file. (MCOL-2181)
After shutdownsystem, first startsystem always fails. ()
ColumnStore Tools for 1.4 were unavailable. ()
postConfigure reports false positive that server is running. ()
postConfigure looks in incorrect location for columnstore.cnf.rpmsave during an upgrade. ()
Multi-node non-systemd installation with replication enabled fails to start. ()
storagemanager.cnf variable $HOME drew path from user's environment. $HOME now points to the current location of ColumnStore data. ()
Changing systemlang in Columnstore.xml to an unrecognized string will prevent ColumnStore startup. ()
Built-in SQL functions do not work in ColumnStore when sql_mode=ORACLE (MCOL-4044)
None.
In alignment to the MariaDB Corporation Engineering Policy, MariaDB ColumnStore 1.4.4 is provided for:
Red Hat Enterprise Linux 8
Red Hat Enterprise Linux 7
CentOS 8
CentOS 7
Ubuntu 20.04
Ubuntu 18.04
Ubuntu 16.04
Debian 10
Debian 9
SUSE Linux Enterprise Server 15
SUSE Linux Enterprise Server 12
Note: MariaDB Enterprise ColumnStore 1.4 is no longer supported. If you would like to deploy Enterprise ColumnStore, please use MariaDB Enterprise ColumnStore 5 or later. For installation and upgrade instructions, see "Deploy".
MCOL-2176 - Jemalloc is a new dependency for MariaDB ColumnStore.
MCOL-1822 - The maximum possible value for AVG() and SUM() has significantly increased due to the usage of long double.
MCOL-901 - group_concat() consumes a great amount of memory
MCOL-1456 - Query doesn't try REDO_PHASE1
MCOL-1559 - Regression on working_tpch1/misc/bug3669 string pad compare not correct
MCOL-1607 - postConfigure must support hostnames as cluster nodes network endpoints.
- causes regression
- WriteEngine bulk methods do not version dictionaries correctly
- Joblist thread pool leaks if mariadb client connection drops its connection early.
- mcsapi stale transactions
- Debian 9 - data-adapter package dependencies broken
- Informatica: delete statement doesn't escape reserved names for column names
- Remote Cpimport / API: Text overlaps MariaDB logo in installer windows
- resumedatabasewrites causes both DDL/DML to go active on um1/um2
- Output of 'select * (with order by limit) queries' returns unexpected result
- RENAME crashes when tablename contains / symbol
- Deb package name change broken
- mxs_adapter throws malloc error
- javamcsapi's shared library gets generated with the version number appended twice
- regr_avgx and regr_avgy should return NULL if count is zero
- regr_intercept, regr_r2, regr_slope and possibly other regr functions should return NULL with only one row.
- javamcsapi - MillionRow test fails on Ubuntu 16.04 and 18.04
- Fix jobstep abort
- Dictionary null comparison check can crash
- ORDER BY with OFFSET in subquery produces random and incorrect result
- IS.columnstore_files maximum contains incorrect number of records for any relation.
- cpimport scientific notation conversion problem
- pentaho kettle adapter lock session with bulk columnstore and dml transaction(delete/update operation).
- PDI CS Bulk Load plugin not able to read transformations with empty configuration
- Autoswitch broken in some cases in 1.2.2
- UDAF docs are currently broken
- PrimProc crash - signal 11, Segmentation fault - funcexp::Func_lpad::getStrVal
- Informatica PowerCenter Bulk Write Connector
- Add Windows builder to buildbot for Kettle
- Add Windows builder to buildbot for mcsimport
- Change the default to use double when overflow occurs in SUM() and AVG()
- Add API test suite to buildbot
- Add data-adapters test suite to buildbot
- Add tools test suite to buildbot
- javamcsapi, pymcsapi known isTableLock and TableLockInfo limitations
- Write Spark and PySpark documentation for mcsapi
- Cant build engine out-of-source
- Check NUMA devel package is installed on BuildBot instances
- Use jemalloc as the main memory allocator - testing for 1.2.3-1
- Rebase 1.2 on
In addition, all bugs fixed in MariaDB ColumnStore 1.2.2 and earlier are implicitly included in this release.
The following procedure outlines upgrading a 1.1.7 ColumnStore install to 1.2.3:
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.
RPM, Debian, and binary packages are provided for the Linux distributions supported by MariaDB ColumnStore 1.2.3 GA version.
The supported OS for the GA version are CentOS 6, CentOS 7, Debian 8, Debian 9, RedHat 6, RedHat 7, SUSE 12, Ubuntu 16.04 and Ubuntu 18.04.
Packages can be downloaded here or can be installed from the repositories.
An Amazon AWS AMI Image is available for this release, please search for AMI name "MariaDB-ColumnStore-1.2.3". 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
Write Data API - Source code for Write Data API /SDK
MaxScale CDC and Kafka Data Adapters -
Beta release of the Streaming Data Adapters: Out of box adapters for data integration between various data sources for specific use cases
is integration of the MaxScale CDC streams into MariaDB ColumnStore
is integration of the Kafka streams into MariaDB ColumnStore.
MCOL-963 - self join cte queries from tpcds alternately fail with parsing error and succeed but with incorrect results
MCOL-976 - System in DBRM_READ_ONLY mode after Non-parent PM recovery under DataRedundancy
MCOL-989 - The addmodule command reported an invalid password error if cluster on the new module is not running
MCOL-997 - postConfigure on a DataRed setup should exiting when system install prompt is answered 'n'
- MySQL replication is not replicating after installation
- LDI and INSERT...SELECT causes mysqld to crash with long VARCHAR entries
- MCS Replication setup failure - mysqld failed to restart
- Debian 9 package: postConfigure failed to create /etc/rc.d/rc.local file
- Replication setup failed when using ssh key and schema sync enabled
- information_schema.columnstore_extents data_size calculation incorrect
- On ovh data center servers, postConfigure crashed on upgrade
- Dictionary deduplication cache is not working correctly
- postConfigure reported system catalog creation error but database continue to work
In addition, all bugs fixed in MariaDB ColumnStore 1.0.11 and earlier are implicitly included in this release.
The following procedure outlines upgrading a 1.1.1 ColumnStore install to 1.1.2:
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-271 empty string values are treated as NULL. This means you cannot insert empty values into a NOT NULL string column.
MCOL-365: Log files created by load data infile remain in the bulk/data/log and /tmp directories. If storage is a concern these can safely be removed.
MCOL-540 : In a non root Ubuntu install with local query enabled, the PM servers crash and restart on table creation.
MCOL-624 :MariaDB 10.2 WF create MEDIAN, PERCENTILE_CONT and PERCENTILE_DISC Window functions. MariaDB ColumnStore 1.1 was rewritten to use the server parser code which does not support the percentile window functions. This will be added in a later release. A median function has been provided instead as part of the User Defined Aggregate Function framework that provides similar functionality or can be adapted to support percentiles other than 0.5.
:Create table caused primproc crashed for a specific configuration
:Implement ha_calpont_impl_rnd_pos. Sorting of long text columns may fail.
:Implement joins between CHAR/VARCHAR and INT columns. ColumnStore now fails more consistently on incompatible join types. Explicit type casts must be used if this error is hit.
: Some functions return "The maximum row size" error when TEXT/LONGTEXT is used in a table
: After adding two PMs with gluster, cpimport failed on newly added PMs. The system must be restarted after adding PM modules with data redundancy / gluster storage.
: Crash when using blob column in 2 subqueries.
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 .
RPM, Debian, and binary packages are provided for the Linux distributions supported by MariaDB ColumnStore 1.1.2 GA version.
The supported OS for the GA version are CentOS 6, CentOS 7, Debian 8, Debian 9, RedHat 6, RedHat 7, SUSE 12, and Ubuntu 16.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.1.2". 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
Write Data API - Source code for Write Data API /SDK
MaxScale CDC and Kafka Data Adapters -
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
- The generated server test DEB package doesn't install
- findobjectfile should report filename for dictionary oid
- change mcsadmin to only allow the module add/remove/disable commands from active PM Module
- columnstore_info's total_usage() and table_usage() reported 0 usage on multi-node configuration
- redistribute data's 'START REMOVE' option did not move data from the requested dbroot
- remove the option of 'mp' in postConfigure
- Amazon ColumnStore AMI support of IAM role with certificates
- replication setup issues when adding modules in combined setup
- merge server 10.1.20 code
- Error in script /usr/local/mariadb/columnstore/bin/rsync.sh
- postConfigure refers to 'Columnstore' instead of 'ColumnStore' as the product
- can't reset autoincrement values
- Add prompt to disable/enable mysql replication in postConfigure
- Error in shell script
- create AlarmConfig.installSave file
- rpm install for multi node combined fails to setup logging on other nodes
- Cannot execute query on mixed engine tables
- Performance improvements to ExeMgr
- 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
empty string values are treated as NULL. This means you cannot insert empty values into a NOT NULL string column.
: 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.
: 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.
: 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 .
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 .
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
Release date: 19th June 2018
MariaDB ColumnStore 1.1.5 is a GA release of MariaDB ColumnStore. This is the fourth release of the MariaDB ColumnStore 1.1 series. This release of MariaDB ColumnStore provides improvements over the previous 1.1.4 GA release.
MariaDB ColumnStore 1.1.5 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.
- Ubuntu 18.04 is supported from this release onwards.
- CPIMPORT fails and Abandoned when data row is too BIG to Handle
- IS.columnstore_columns crashes when DDL is simultaneously executing
- mcsapi Python wrapper breaks on out of source builds
- bulk write sdk python bindings does not support status out param in setColumn
In addition, all bugs fixed in MariaDB ColumnStore 1.1.4 and earlier are implicitly included in this release.
The following procedure outlines upgrading a 1.1.4 ColumnStore install to 1.1.5:
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.
empty string values are treated as NULL. This means you cannot insert empty values into a NOT NULL string column.
: 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.
: In a non root Ubuntu install with local query enabled, the PM servers crash and restart on table creation.
: WF create MEDIAN, PERCENTILE_CONT and PERCENTILE_DISC Window functions. MariaDB ColumnStore 1.1 was rewritten to use the
RPM, Debian, and binary packages are provided for the Linux distributions supported by MariaDB ColumnStore 1.1.5 GA version.
The supported OS for the GA version are CentOS 6, CentOS 7, Debian 8, Debian 9, RedHat 6, RedHat 7, SUSE 12, Ubuntu 16.04 and Ubuntu 18.04.
Packages can be downloaded or can be installed from the .
An Amazon AWS AMI Image is available for this release, please search for AMI name "MariaDB-ColumnStore-1.1.5". 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 -
Tools -
Write Data API -
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
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
- A build related performance regression in the 1.0.2 release has been fixed restoring performance to be comparable with the prior Infinidb versions.
- MariaDB ColumnStore no longer issues snmp traps. As a result of this 2 prompts are removed from the postConfigure script relating to this.
- the WEEK and YEARWEEK functions are now consistent with the MariaDB server implementation.
- 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
- Create table failed due to Error updating BRM block version buffer overflow error
- Nth_value() windowing function does not exist error
- Last_value() Windowing function returned an syntax error
- ROUND() function returns incorrect value
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 .
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.
: Following three window functions do not return correct value
FIRST_VALUE
LEAD
LAG
: 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 .
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
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
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 -
Release date: 24th April 2018
MariaDB ColumnStore 1.1.4 is a GA release of MariaDB ColumnStore. This is the fourth release of the MariaDB ColumnStore 1.1 series. This release of MariaDB ColumnStore provides improvements over the previous 1.1.3 GA release.
MariaDB ColumnStore 1.1.4 is a GA release.
For an overview of MariaDB ColumnStore see
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
release of Pentaho Kettle Adapter for integration of MariaDB ColumnStore utilizing Pentaho Kettle.
- The base MariaDB server version is now which include several maintenance and security fixes.
- The Python bulk write SDK binding has an API change around setColumn() to return a status.
- After adding two PMs, cpimport failed on newly added PMs
- table_usage() stored procedure show zero total usage when there are no dict columns
- Incorrect 0 row(s) affected on delete
- Cross-engine join query failing (single node)
In addition, all bugs fixed in MariaDB ColumnStore 1.1.3 and earlier are implicitly included in this release.
The following procedure outlines upgrading a 1.1.3 ColumnStore install to 1.1.4:
Multi version upgrades generally will work using the same procedure however we can't test every possible permutation so you should test your specific scenario outside of production first if you wish to try this (and this is good practice regardless).
There are a number bugs and known limitations within this version of MariaDB ColumnStore, the most serious of these are listed below.
empty string values are treated as NULL. This means you cannot insert empty values into a NOT NULL string column.
: 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.
: In a non root Ubuntu install with local query enabled, the PM servers crash and restart on table creation.
: WF create MEDIAN, PERCENTILE_CONT and PERCENTILE_DISC Window functions. MariaDB ColumnStore 1.1 was rewritten to use the
RPM, Debian, and binary packages are provided for the Linux distributions supported by MariaDB ColumnStore 1.1.4 GA version.
The supported OS for the GA version are CentOS 6, CentOS 7, Debian 8, Debian 9, RedHat 6, RedHat 7, SUSE 12, and Ubuntu 16.04.
Packages can be downloaded or can be installed from the .
An Amazon AWS AMI Image is available for this release, please search for AMI name "MariaDB-ColumnStore-1.1.4". AMI specific installation instructions can be found .
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 -
Tools -
Write Data API -
Release date: 7th September 2018
is a GA release of MariaDB ColumnStore. This is the fourth release of the MariaDB ColumnStore 1.1 series. This release of MariaDB ColumnStore provides improvements over the previous 1.1.5 GA release.
MariaDB ColumnStore 1.1.6 is a release.
For an overview of see
Please provide feedback in 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 or subscribe to mariadb-columnstore@googlegroups.com
Release date: 18th September 2017
is a Beta release of MariaDB ColumnStore. This is the first release of the MariaDB ColumnStore 1.1 series. The MariaDB ColumnStore 1.1 series provides several new features and improvements over the MariaDB ColumnStore 1.0 release.
MariaDB ColumnStore 1.1.0 is a release.
Do not use beta releases on production systems!
For an overview of see
Release date: 3rd November 2017
is a Release Candidate release of MariaDB ColumnStore. This is the second release of the MariaDB ColumnStore 1.1 series. The MariaDB ColumnStore 1.1 series provides several new features and improvements over the MariaDB ColumnStore 1.0 release.
MariaDB ColumnStore 1.1.1 is a release.
Do not use Release Candidate releases on production systems!
For an overview of see
Please provide feedback in 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 or subscribe to mariadb-columnstore@googlegroups.com
MCOL-1342 - A restriction for allowed length of the table and column names is not implemented
MCOL-1348 - ExeMgr failes to process SELECT with any field preceding UDAF functor.
MCOL-1349 - Selecting VIEW throws 1815. Internal error when the VIEW definition contains nested and non nested LEFT JOINS and On clause filter on the nested JOIN
MCOL-1359 - Spark connector does not allow NULL values
MCOL-1361 - Spark connector doesn't handle null values
MCOL-1370 - Network Error incorrect handled, Amazon DBROOT detach failed, but dbroot still was reassigned
MCOL-1377 - ColumnStore system logging not working after 1.1.4 ubuntu-16 install
MCOL-1384 - Couldn't use reserved words in idents even with quotes(backport from develop)
MCOL-1390 - SUBSTRING_INDEX returns NULL when the number parameter is negative
MCOL-1394 - kafka avro adapter install avro library issues
MCOL-1396 - VARCHAR returning NULL when StringStore memory limit exceeded
MCOL-1400 - update pdi data adapter to use explicit mcsapi version numbers
MCOL-1403 - Trailing whitespace in CHAR/VARCHAR break string matches - Revisited
MCOL-1405 - Mysqld PID is missed in the output of mcsadmin getSystemInfo
MCOL-1406 - Cannot create pv_facts table in develop
MCOL-1408 - Columnstore table unable to accept writes after thousands of commits via Bulk SDK
MCOL-1430 - CDC Connector v2.2.5-1 unable to connect to MaxScale
MCOL-1440 - rename the data-adapter kettle package to match the others
MCOL-1444 - mcsapi's dataconvert-decimal fails for Ubuntu 18.04
MCOL-1455 - mariadb-columnstore-kafka-adapters has been deprecated - remove from building
MCOL-1460 - Build for Kettle adapter is not created
MCOL-1463 - Columnstore provided udf median()/avg_mode() not working
MCOL-1179 - Pentaho Data Integration / Kettle - Bulk API Java Binding
MCOL-1232 - Spark connector - support different ColumnStore configurations
MCOL-1259 - ColumnStore Data-Adapters needs a top level cmake for building all Data-Adapters
MCOL-1344 - CREATE table STATEMENT from Spark Dataframe structure
MCOL-1364 - Update mariadb-columnstore-api package names to amd64 in make file for Debian/Ubuntu
MCOL-1412 - Backport Ubuntu 18.04 support to 1.1
MCOL-1435 - Merge MariaDB 10.2.15 into 1.1
MCOL-631 :Create table caused primproc crashed for a specific configuration
MCOL-643 :Implement ha_calpont_impl_rnd_pos. Sorting of long text columns may fail.
MCOL-695 :Implement joins between CHAR/VARCHAR and INT columns. ColumnStore now fails more consistently on incompatible join types. Explicit type casts must be used if this error is hit.
MCOL-713 : Some functions return "The maximum row size" error when TEXT/LONGTEXT is used in a table
MCOL-1224: post-install non-root has incorrect permissions for /etc/rc.local
MCOL-1225: LD_LIBRARY_PATH not set correctly in centos6 non-root install
MCOL-1491: auth_pam.so plugin missing from server package
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 .
MaxScale CDC and Kafka Data Adapters - Source Code for data adapters
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
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:
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 .
MCOL-1196 - Error when using OR in case THEN portion
MCOL-1213 - SystemCatalog.getTable("table name") doesn't support uppercase letters
MCOL-1217 - newly added user module didnt have mysql replication slave setup
MCOL-1222 - ColumnStore start/restart can return before system is ready
MCOL-1228 - ALTER TABLE...CHANGE COLUMN broken for TEXT data types
MCOL-1230 - Change spark-connector's default compile option to ON
MCOL-1231 - Get a cmake error while building releases without both Python versions installed instead of a warning
MCOL-1233 - Ubuntu package has a bad dependency
MCOL-1234 - Nested CASE filters not processed
MCOL-1235 - procmgr crash - too many files open on alarm socket
MCOL-1241 - Move ColumnStore Kettle plugin to data-adapters git repository
MCOL-1245 - getting A fatal error in bulkinsert mariadb columnstore java api
MCOL-1246 - Trailing whitespace in CHAR/VARCHAR break string matches
MCOL-1252 - CSV load into columnstore table using Pentaho adapter with CS Bulk Import plugin doesn't succeed
MCOL-1255 - PDI CS Bulk Load plugin can't work with variable defined in kettle.properties file
MCOL-1262 - PDI CS naming conventions support
MCOL-1280 - MCSAPI C++ documentation, example incorrect
MCOL-1285 - Adapter can't recognize database schema with capital letters
MCOL-1317 - Columnstore Cluster Tester tool does not check the availability of all ports needed to mcs operations
MCOL-1321 - bulk write sdk python bindings does not support status out param in setColumn
MCOL-1323 - cpimport Splitter has incorrect SIGPIPE mapping
MCOL-1179 - Pentaho Data Integration / Kettle - Bulk API Java Binding
MCOL-1232 - Spark connector - support different ColumnStore configurations
MCOL-1283 - Try to pack/load the shared bulk write sdk library in/from jar to ease installation process
MCOL-1296 - Add debug output as an API option
MCOL-1312 - PDI version number - include git
MCOL-1318 - Columnstore Cluster Tester tool is evaluating Failure if Firewall Services or SELINUX are enabled
MCOL-1264 - List of manual tests performed
MCOL-1319 - Merge MariaDB 10.2.14
MCOL-1333 - Document that .tar.gz of RPM files is needed for addModule command
MCOL-1261 - mcsapi Python wrapper breaks on out of source builds
MCOL-1325 - rename table fails when database different than current database
MCOL-1344 - CREATE table STATEMENT from Spark Dataframe structure
MCOL-631 :Create table caused primproc crashed for a specific configuration
MCOL-643 :Implement ha_calpont_impl_rnd_pos. Sorting of long text columns may fail.
MCOL-695 :Implement joins between CHAR/VARCHAR and INT columns. ColumnStore now fails more consistently on incompatible join types. Explicit type casts must be used if this error is hit.
MCOL-713 : Some functions return "The maximum row size" error when TEXT/LONGTEXT is used in a table
MCOL-1224: post-install non-root has incorrect permissions for /etc/rc.local
MCOL-1225: LD_LIBRARY_PATH not set correctly in centos6 non-root install
MCOL-1491: auth_pam.so plugin missing from server package
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 .
MaxScale CDC and Kafka Data Adapters - Source Code for data adapters
MCOL-970 - MariaDB's slow query log only logging vtable information
MCOL-1037 - Race condition in FIFO buffer
MCOL-1155 - NOT with null safe operator fails
MCOL-1195 - mcsapi BadUsage.AssertTableLock test creates phantom transaction
- mcsapi won't compile with Python3 in Debug mode in CentOS 7
- test200 needs tuning
- mcsapi Java test fails on Ubuntu 18.04 and Java 10
- mcsapi doesn't detect when WriteEngineServer has gone away
- CDC adapter: mxs_adapter doesn't measure transaction insert time as expected
- where does not properly evaluate case when case when on varchar columns
- PriorityThreadPool can crash
- Data-Adapter package has different names for RPM and DEB
- auth_pam.so plugin missing from server package
- Installation failed in Replication Distribution command
- Non-root Install - core dumps not working
- Incorrect 0 row(s) affected on delete with cross engine join
- ColumnStore fails to make inner join if using CASE in predicate.
- Case when~ vs case ~ when ~
- Compiler error in GCC 8.1
- mcsapi documentation build issue in CentOS 7
- ColumnStore as root crashes processes using shm
- javamcsapi ColumnStoreBulkInsert can't manually be garbage collected
- mxs_adapter requires -t to gracefully exit
- mxs_adapter state file is stored in the current directory
- sendAlarmReport error: InetStreamSocket::connect: connect() error: Connection timed
- python spark connector - broken
- insert into select crashes for a BLOB column
- Yacc debug hard coded on
- data-adatper centos7 package rename not executed
- Incorrect HWM calculation if the table's first column width > 1
- Performance Schema crashes prepared statement
- check hardcoded uses of root user for mysql
- Make ColumnStore work under valgrind
- Support Ubuntu 18.04
- Improve cross engine error handling
- Use condition pushdown in I_S tables
- Java - mcsapi - introduce new function getJavaMcsapiVersion()
- Backward / Forward compatibility test for javamcsapi and mcsapi
- Ability to configure ColumnStore to use domain names instead of IP addresses
- add UMASK check to ColumnStore Cluster Tester script
- mxs_adapter multi-table support
- Transform CDC events into UPDATE and DELETE statements
- One step configuration of Single Server Node
- One step configuration of Multi Server Node
- Documentation for Python API missing
- Merge
- remove generated build doc from mcsapi in favor of its Readme.md in Github
- Update ColumnStore docs for 18.04
- Joiner array boundary bug
In addition, all bugs fixed in MariaDB ColumnStore 1.1.5 and earlier are implicitly included in this release.
The following procedure outlines upgrading a 1.1.5 ColumnStore install to 1.1.6:
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-271 empty string values are treated as NULL. This means you cannot insert empty values into a NOT NULL string column.
MCOL-365: Log files created by load data infile remain in the bulk/data/log and /tmp directories. If storage is a concern these can safely be removed.
MCOL-540 : In a non root Ubuntu install with local query enabled, the PM servers crash and restart on table creation.
MCOL-624 :MariaDB 10.2 WF create MEDIAN, PERCENTILE_CONT and PERCENTILE_DISC Window functions. MariaDB ColumnStore 1.1 was rewritten to use the server parser code which does not support the percentile window functions. This will be added in a later release. A median function has been provided instead as part of the User Defined Aggregate Function framework that provides similar functionality or can be adapted to support percentiles other than 0.5.
:Create table caused primproc crashed for a specific configuration
:Implement ha_calpont_impl_rnd_pos. Sorting of long text columns may fail.
:Implement joins between CHAR/VARCHAR and INT columns. ColumnStore now fails more consistently on incompatible join types. Explicit type casts must be used if this error is hit.
: Some functions return "The maximum row size" error when TEXT/LONGTEXT is used in a table
: post-install non-root has incorrect permissions for /etc/rc.local
: LD_LIBRARY_PATH not set correctly in centos6 non-root install
: The QueryStats table is missing
/dev/shm may be set to 755 permissions prior to 1.1.6 which could cause problems with other non-root processes, from 1.1.6 onwards ColumnStore does not try to do this. You should change this to 777 if it is causing problems with your installation.
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 .
RPM, Debian, and binary packages are provided for the Linux distributions supported by MariaDB ColumnStore 1.1.6 GA version.
The supported OS for the GA version are CentOS 6, CentOS 7, Debian 8, Debian 9, RedHat 6, RedHat 7, SUSE 12, Ubuntu 16.04 and Ubuntu 18.04.
Packages can be downloaded here or can be installed from the repositories.
An Amazon AWS AMI Image is available for this release, please search for AMI name "MariaDB-ColumnStore-1.1.6". 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
Write Data API - Source code for Write Data API /SDK
MaxScale CDC and Kafka Data Adapters -
MariaDB ColumnStore 1.1.0 is based on MariaDB Server 10.2.8
The Window functions have been re-implemented with MariaDB Server 10.2.8 code.
Text and Blob Data Types.
.
MariaDB Server .
Built-in data redundancy using GlusterFS integration for installations that use local disks for data storage on PMs. Please refer to for using GlusterFS with MariaDB ColumnStore.
Several performance improvements in string handling, memory utilization and general area.
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-1 - Query Failed after a redistributeDB while ddl/dml/queries were active
MCOL-267 - TEXT and BLOB data types are not supported
MCOL-317 - replace drizzle with maria client library
MCOL-318 - switch to using os distribution version of snappy
- BLOB data type not supported
- columnstore queries show as vtable query rather than original query in audit log
- binary package install doesnt check for package dependencies
: gluster storage option in installer fails with an error.
- update default replication configuration
- warning error reported after upgrade to 1.0.6
- More performance improvements to ExeMgr
- native write data api
- analyze and implement thread pools and memory buffers for performance optimization
- backup (cold) and restore tool
- productize glusterfs support and add tools to automate
- support pre-installed software in postConfigure and addModule - phase I
- support user defined aggregate functions
- postCfg upgrade output refers to calpont
- Possible mem leak and crash in columnstore's mysqld
- "Too many open files" errors during DBT3 performance test
- Can't create view by using ColumnStore's windowing funcion SQL
- Cross Engine step tries to use a bad UDS path for localhost
- Enabled harderning compile flags
- create front end for "VAR_SAMP" window function
- create "STDDEV_SAMP" Windows function
- getSystemResourceUsage doesnt work on non-root install
- Performance improvement with string handling
- Add BLOB/TEXT detection
- Restarting installation fails if installed on secondary interface
- TEXT columns need to support the same functions as VARCHAR
- calsettrace(1) can cause a mysqld crash
- Columnstore executes join on incompatible types
- Using BETWEEN together with date functions in WHERE clause 100x slower than InfiniDB
- multi node package install with non login su won't start
- postConfigure should check for local rpm / bins existing
- Columnstore Cluster Test Tool - add check for mariadb-libs base install
- run command to create system tables after startsystem
- INSERT...SELECT with window functions fail
- mysqld not shutdown by shutdownsystem commands, sometimes
- could not open file for OID after a outage recover from pm2 PrimProc
- Merge
- 1.0.11 upgrade failed when base directory is nfs mounted
In addition, all bugs fixed in MariaDB ColumnStore 1.0.11 and earlier are implicitly included in this release.
Multi version upgrades are not supported, please upgrade versions prior to 1.0.11 before upgrading to 1.1.0:
There are a number bugs and known limitations within this version of MariaDB ColumnStore, the most serious of these are listed below.
MCOL-271 empty string values are treated as NULL. This means you cannot insert empty values into a NOT NULL string column.
MCOL-365: Log files created by load data infile remain in the bulk/data/log and /tmp directories. If storage is a concern these can safely be removed.
MCOL-540 : In a non root Ubuntu install with local query enabled, the PM servers crash and restart on table creation.
MCOL-624 :MariaDB 10.2 WF create MEDIAN, PERCENTILE_CONT and PERCENTILE_DISC Window functions. MariaDB ColumnStore 1.1 was rewritten to use the server parser code which does not support the percentile window functions. This will be added in a later release. A median function has been provided instead as part of the User Defined Aggregate Function framework that provides similar functionality or can be adapted to support percentiles other than 0.5.
:Create table caused primproc crashed for a specific configuration
:Implement ha_calpont_impl_rnd_pos. Sorting of long text columns may fail.
:Implement joins between CHAR/VARCHAR and INT columns. ColumnStore now fails more consistently on incompatible join types. Explicit type casts must be used if this error is hit.
: Some functions return "The maximum row size" error when TEXT/LONGTEXT is used in a table
: Recursive Common Table Expressions caused mysqld to crash
: INSERT after ALTER TABLE can corrupt HWM
: fter adding two PMs with gluster, cpimport failed on newly added PMs. The system must be restarted after adding PM modules with data redundancy / gluster storage.
: Gluster failover: Stack did not recover completely after PM1 reboot. Under certain topologies (replication count < pm count) failover may not work correctly. Recommend limiting testing to replication count = pm count.
: multiple application of a UDAF on the same column will result in a null value except for the first occurence.
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 .
RPM, Debian, and binary packages are provided for the Linux distributions supported by MariaDB ColumnStore 1.1.0 Beta 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.1.0". 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
Write Data API - Source code for Write Data API /SDK
MariaDB ColumnStore 1.1.1 is based on MariaDB Server 10.2.10
Java and Python bindings are available for the Write Data API
MCOL-662 - Unexpected results in cross engine join
MCOL-667 - Installation of MCS updates the root .bashrc file
MCOL-750 - make the remote server install scripts run faster by checking for ssh/scp return codes
MCOL-783 - Recursive Common Table Expressions caused mysqld to crash
- redistribute remove moved data from removed node to one node
- Running TRUNCATE on many tables in parallel seems to eventually deadlock
- Not all data escaped when inserting with select statement from innodb table into columnstore
- INSERT after ALTER TABLE can corrupt HWM
- NULL operand ignored in vtable mode when querying view
- exemgr crashes with a nested aggregate multiplication query
- DistributeConfigFile Failed messages after adding modules
- Warning messages for the RemoveModule command should be improved
- Improve the output from the RemoveModule command
- Gluster failover: Stack did not recover completely after PM1 reboot
- UDAF returns null for 2nd or more applications against same column
- postConfigure is not detecting glusterfs on Debian9.1 for non-root user
- switchparentoammodule cores when pm2 is active on a 1um/2pm Data Redundancy system
- columnstore replication failover from master updates server-id
- multi-node postConfigure fails when mysql password is set.
- coalesce with count(distinct) can lead to incorrect results
- MariaDBReplication slave messages is incorrectly sending updates to PM nodes
- migrate to swig for mcsapi python binding
- tpcds query 17 fails with invalid colum width
- invalid LD_LIBRARY_PATH for non root install
- self join cte queries from tpcds alternately fail with parsing error and succeed but with incorrect results
- group_contact with order by on joined table causes error
- 1.0 to 1.1 non-root upgrade issue - problem shows after a reboot, still using 1.0 ENV variables
- PmMaxMemorySmallSide configuration value not carried forward in upgrade
- ArithmaticColumn parsing can cause crash
- Crash with LEAD function in ColumnStore with 'char' field type
- Merge into ColumnStore
- Error 1815 after several executions of example/basic_bulk_insert having SMALLINT in t1
- 1um/2pm DataRep system starting up without a ProcessManager in HOT_STANDBY state
- provide a resetRow method
- java binding for mcsapi
- Merge
In addition, all bugs fixed in MariaDB ColumnStore 1.0.11 and earlier are implicitly included in this release.
Multi version upgrades are not supported, please upgrade versions prior to 1.1.0 before upgrading to 1.1.1:
There are a number bugs and known limitations within this version of MariaDB ColumnStore, the most serious of these are listed below.
MCOL-271 empty string values are treated as NULL. This means you cannot insert empty values into a NOT NULL string column.
MCOL-365: Log files created by load data infile remain in the bulk/data/log and /tmp directories. If storage is a concern these can safely be removed.
MCOL-540 : In a non root Ubuntu install with local query enabled, the PM servers crash and restart on table creation.
MCOL-624 :MariaDB 10.2 WF create MEDIAN, PERCENTILE_CONT and PERCENTILE_DISC Window functions. MariaDB ColumnStore 1.1 was rewritten to use the server parser code which does not support the percentile window functions. This will be added in a later release. A median function has been provided instead as part of the User Defined Aggregate Function framework that provides similar functionality or can be adapted to support percentiles other than 0.5.
:Create table caused primproc crashed for a specific configuration
:Implement ha_calpont_impl_rnd_pos. Sorting of long text columns may fail.
:Implement joins between CHAR/VARCHAR and INT columns. ColumnStore now fails more consistently on incompatible join types. Explicit type casts must be used if this error is hit.
: Some functions return "The maximum row size" error when TEXT/LONGTEXT is used in a table
: fter adding two PMs with gluster, cpimport failed on newly added PMs. The system must be restarted after adding PM modules with data redundancy / gluster storage.
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 .
RPM, Debian, and binary packages are provided for the Linux distributions supported by MariaDB ColumnStore 1.1.1 RC 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.1.0". 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
Write Data API - Source code for Write Data API /SDK
Release date: 21st February 2019
MariaDB ColumnStore 1.1.7 is a GA release of MariaDB ColumnStore. This is the fourth release of the MariaDB ColumnStore 1.1 series. This release of MariaDB ColumnStore provides improvements over the previous 1.1.6 GA release.
MariaDB ColumnStore 1.1.7 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.
- Use jemalloc as the main memory allocator. Please ensure jemalloc is installed on each ColumnStore node prior to installation or upgrade.
- Incorrectly formatted file can cause cpimport to crash and leave behind locks
- assertion 'fColumn.get() && fSub && fFunc' failed , caused lost connection to MySQL server during query and crash of mysql
- Adapter can't recognize database schema written with backtick
- data corruption when setting NUMERIC columns to NULL through the python and C++ API
In addition, all bugs fixed in MariaDB ColumnStore 1.1.6 and earlier are implicitly included in this release.
The following procedure outlines upgrading a 1.1.6 ColumnStore install to 1.1.7:
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.
empty string values are treated as NULL. This means you cannot insert empty values into a NOT NULL string column.
: 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.
: In a non root Ubuntu install with local query enabled, the PM servers crash and restart on table creation.
: WF create MEDIAN, PERCENTILE_CONT and PERCENTILE_DISC Window functions. MariaDB ColumnStore 1.1 was rewritten to use the
RPM, Debian, and binary packages are provided for the Linux distributions supported by MariaDB ColumnStore 1.1.7 GA version.
The supported OS for the GA version are CentOS 6, CentOS 7, Debian 8, Debian 9, RedHat 6, RedHat 7, SUSE 12, Ubuntu 16.04 and Ubuntu 18.04.
Packages can be downloaded or can be installed from the .
An Amazon AWS AMI Image is available for this release, please search for AMI name "MariaDB-ColumnStore-1.1.7". 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 -
Tools -
Write Data API -
MariaDB ColumnStore is a columnar storage engine. This is the first release in the ColumnStore 1.4 series. This release contains new features and fixes, compared to MariaDB ColumnStore 1.2.5.
This release of MariaDB ColumnStore is included with .
MariaDB ColumnStore 1.4.2 was released on 2020-01-06.
Release date: 17th October 2018
is an Alpha release of MariaDB ColumnStore. This is the first release of the MariaDB ColumnStore 1.2 series. The MariaDB ColumnStore 1.2 series provides several new features and improvements over the MariaDB ColumnStore 1.1 release.
MariaDB ColumnStore 1.2.0 is a release.
Do not use alpha releases on production systems!
For an overview of see
Please provide feedback in 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 or subscribe to mariadb-columnstore@googlegroups.com
:msg,contains,"CAL0071: InetStreamSocket::read: timeout during readToMagic: socket read error: Success; InetStreamSocket:" ~MCOL-1347 - ALTER TABLE ADD COLUMN creates a column with incorrect width for a varchar columns.
MCOL-1459 - CDC adapter: Name of the cpio file is different from the name of rpm package
MCOL-1505 - ExeMgr can crash in cleanTmpDir()
MCOL-1507 - ExeMgr over using memory causing swap and system restarts to occur
MCOL-1523 - OAM Process failover logic for DDLproc is incorrect - causing DDL to stop working
MCOL-1554 - PDI CS not work in the Pentaho Sever repository
MCOL-1563 - Data corruption when inserting out-of-bounds data
MCOL-1606 - PDI 8 - variable substitution doesn't work
MCOL-1643 - PDI plugin CI tests - minor changes in redme file are needed
MCOL-1648 - pymcsapi3 on Windows depends on the Python 3 release DLL it was compiled with
MCOL-1654 - Querystats table is broken
MCOL-1658 - support space names in columnstore table column names
MCOL-1659 - Unable to have spaces in column names in ddl
MCOL-1660 - Table naming does not allow for spaces
MCOL-1662 - WriteEngine bulk methods do not version dictionaries correctly
MCOL-1676 - AVG as Window function with OVER(sort by) gives bad answer.
MCOL-1694 - Add better logging for uncaught exceptions in DDLProc/DMLProc
MCOL-1695 - Add OS information to Kettle zip file
MCOL-1701 - Change Windows mcsapi build to use libraries from external directory
MCOL-1702 - Joblist thread pool leaks if mariadb client connection drops its connection early.
MCOL-1704 - javamcsapi - compatibility test fails if executed multiple times
MCOL-1709 - DDL for creation of a new table in columnstore produces syntax error when it runs on columnstore
MCOL-1720 - ColumnStoreDateTime(dateTime, format) can not be initialized on Debian 9
MCOL-1726 - mcsapi stale transactions
MCOL-1746 - Error while connecting to the MariadDB maxscale with tx
MCOL-1750 - Thread stack memory leak in ThreadPool
MCOL-1761 - Test script for Win is searching for wrong named zip file
MCOL-1766 - Increase Gradle dependency resolution timeout to 5min
MCOL-1797 - resumedatabasewrites causes both DDL/DML to go active on um1/um2
MCOL-1810 - setConfig can hang on low core count
MCOL-1826 - PrimProc crash in float/double to string conversion
MCOL-1829 - Output of 'select * (with order by limit) queries' returns unexpected result
MCOL-1852 - Spark Exporter uses collect() instead of toLocalIterator() on DataFrames to export and therefore uses too much memory on the Driver
MCOL-1868 - func_concat_ws type
MCOL-1887 - PDI Kettle Plugin help page
MCOL-1945 - mxs_adapter throws malloc error
MCOL-1947 - Our aliases break BASH
MCOL-2007 - Add git version information to builds
MCOL-2009 - Fix jobstep abort
MCOL-2018 - Dictionary null comparison check can crash
MCOL-2052 - IS.columnstore_files maximum contains incorrect number of records for any relation.
MCOL-2062 - cpimport scientific notation conversion problem
MCOL-2070 - pentaho kettle adapter lock session with bulk columnstore and dml transaction(delete/update operation).
MCOL-2071 - PDI CS Bulk Load plugin not able to read transformations with empty configuration
MCOL-2136 - Use jemalloc as the main memory allocator
MCOL-1633 - mcsapi Windows - add needed Windows Redistributables to installer
MCOL-1644 - PDI plugin CI tests - add check with PDI 8
MCOL-1670 - Windows mcsapi - add option to install libraries directly into Python
MCOL-1671 - Windows mcsapi - add option to install libraries directly into Java
MCOL-1698 - Add Distinct capability to specific UDAnF Window Functions
MCOL-1340 - Remove dpkg purge from docs
MCOL-1634 - Include Windows library build into mcsapi
MCOL-1713 - Add Windows suffix to kettle data adapter
MCOL-1743 - Documentation issue in repoinstallation of columnstore-kafka-adapter
MCOL-1744 - Remove unnecessary CentOS 7 mcsapi package dependencies
MCOL-1754 - Change libmysql dependency for Windows api tests to libmariadb
MCOL-2005 - Merge MariaDB 10.2.21 into develop-1.1
MCOL-2107 - execute tpc-ds performance test suite on dev v1.1.7 with purpose of regression performance testing
MCOL-2120 - Check NUMA devel package is installed on BuildBot instances
MCOL-2158 - Merge MariaDB 10.2.22
MCOL-631 :Create table caused primproc crashed for a specific configuration
MCOL-643 :Implement ha_calpont_impl_rnd_pos. Sorting of long text columns may fail.
MCOL-695 :Implement joins between CHAR/VARCHAR and INT columns. ColumnStore now fails more consistently on incompatible join types. Explicit type casts must be used if this error is hit.
MCOL-713 : Some functions return "The maximum row size" error when TEXT/LONGTEXT is used in a table
MCOL-1224: post-install non-root has incorrect permissions for /etc/rc.local
MCOL-1225: LD_LIBRARY_PATH not set correctly in centos6 non-root install
/dev/shm may be set to 755 permissions prior to 1.1.6 which could cause problems with other non-root processes, from 1.1.6 onwards ColumnStore does not try to do this. You should change this to 777 if it is causing problems with your installation.
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 .
MaxScale CDC and Kafka Data Adapters - Source Code for data adapters
Until now, MariaDB ColumnStore has been maintained as a custom fork of MariaDB Server, to handle the unique way that queries are handled for distributed processing.
With this release, a joint project between the MariaDB Server and MariaDB ColumnStore engineering teams, ColumnStore now works as a pluggable storage engine on the standard MariaDB Enterprise Server 10.4 platform.
MariaDB Enterprise Server 10.4 includes distributed processing engine support features. These features are not present in the older 10.3 and 10.2 release series.
A standard MariaDB Server is now used for ColumnStore UM (User Module) nodes. ColumnStore users can now enjoy the benefits of MariaDB Server 10.4, and MariaDB Server 10.4 users are now able to deploy ColumnStore on top of their existing stack.
MariaDB ColumnStore now has the ability to use any object store that is Amazon S3 API compatible. The new Storage Manager uses a persistent disk cache for read/write operations so that it has minimal performance impact on ColumnStore. In some cases it will perform better than local disk operations.
Usage instructions:
Before running postConfigure, edit the storagemanager.cnf configuration file to specify the S3 connection parameters (as detailed in the S3 section of that file), and the local machine configuration (as detailed in the ObjectStorage and Cache sections). The configuration file is documented in-line. Enable the Storage Manager by setting ObjectStorage/Service to S3
Run postConfigure, and when promoted for type of storage, select the StorageManager option.
cpimport is a high-speed bulk data loading utility for ColumnStore. cpimport now includes command-line options for loading a CSV file from Amazon S3 (and compatible) buckets.
-y
S3 Authentication Key
-K
S3 Secret Key
-t
S3 Bucket
-H
S3 Hostname (omit if using Amazon S3, this is the default)
-g
S3 Region
When these options are set, cpimport will use the path/filename provided to load an object from object storage instead of a local file. Current behavior is to download the entire file into memory before processing.
Please note that for cpimport the current system time of the PM node is used.
The MODA() UDAF (User-Defined Aggregate Function) determines the mode average. MODA() has tie-break behavior to use the closest to the average, and then the smallest absolute value.
Statement-based replication into ColumnStore tables is supported by setting columnstore_replication_slave=on on the UM that will apply the replication data. Row-based replication events on ColumnStore replica (slave) tables will currently fail, generating an error viewable with SHOW SLAVE STATUS
The performance of BRM (Block Resolution Manager) snapshots has been increased for improved performance when committing data to ColumnStore.
To reduce SSD wear and increase write performance for large data sets containing many columns, ColumnStore now allocates disk as-needed, writing only real data and padding to fill the remainder of an 8KB block. ColumnStore previously wrote twice -- once to pre-allocate an empty file for each new extent (8 million item file for a column), and a second time to fill the file with real data.
The outer "ORDER BY" of a query is now processed using ColumnStore's engine instead of MariaDB server. This uses a faster sorting algorithm for higher performance with larger result sets.
Joins use a new hash algorithm which is significantly faster and requires significantly less initial memory to execute.
Memory cleanup after query execution now occurs in a separate thread. This previously occurred in the main ExeMgr thread, which could delay execution of new queries.
ColumnStore 1.2 and earlier included the InfiniDB engine as an alias. This alias has now been removed. All ColumnStore tables must now be created with the engine name "columnstore". All MariaDB system variables prefixed with "infinidb_" have now been removed.
vtable has been replaced with a set of query execution handlers: Select Handler, Derived Handler, and table API mode.
The vtable mode switch (infinidb_vtable_mode system variable) has been eliminated. Two new session variables have been added: columnstore_select_handler, columnstore_derived_handler
The Select Handler is the replacement for a vtable, and is the default query execution handler. It is expected to provide the fastest execution path for the whole query.
Select Handler lacks support for some vtable features, including:
Cartesian JOIN
Non-Equi JOIN
INSERT .. SELECT
SELECT INTO OUTFILE
If the Select Handler fails to execute a query, an error is returned. If a query fails under the Select Handler, set columnstore_select_handler=off for the session. This will cause the Server to hand-off query execution to the Derived Handler. The query must be restarted after the session variable has been set.
If the Derived Handler fails to execute a query, an error is returned. If a query fails under both the Select Handler and Derived Handler, set columnstore_select_handler=off and columnstore_derived_handler=off for the session. This will cause table API execution, an equivalent to disabled vtable mode in ColumnStore 1.2.x and earlier. The query must be restarted after the session variables have been set.
ColumnStore 1.4 is included with MariaDB Enterprise Server 10.4 on select Platforms.
ColumnStore is available for deployment from package tarball and repository. ColumnStore is not available for deployment from binary tarballs.
The "distributed install" method which pushed packages onto other nodes during postConfigure has been removed. ColumnStore packages must now be installed on all nodes prior to startup.
ColumnStore XML configuration files have moved to /etc/columnstore
MariaDB Enterprise Server configuration options for ColumnStore have moved to /etc/my.cnf.d/columnstore.cnf and the default MariaDB Enterprise Server my.cnf will load this file.
The ColumnStore data directory has moved to /var/lib/columnstore and is separate from the MariaDB Server data directory at /var/lib/mysql
ColumnStore binaries have moved to /usr/bin or /usr/sbin, and the libraries are in the OS standard /usr library path. Some ColumnStore binaries have been renamed to avoid conflict, including:
post-install
columnstore-post-install
getConfig
mcsGetConfig
setConfig
mcsSetConfig
Cross-engine joins depend on TCP connection from ExeMgr to the Server process. Since the database root user in MariaDB Enterprise Server 10.4 authenticates only by UNIX socket, a dedicated user must be created to support cross-engine joins. The cross engine section of Columnstore.xml should be edited accordingly.
DBRM files could be deleted during a failover scenario. (MCOL-2152)
Certain window function queries could crash the Server process. (MCOL-3434)
group_concat() with DISTINCT concatenates even non-distinct values. (MCOL-2146)
Wrong results could be returned for a complex query with subquery and window functions over decimal(12,4) column. (MCOL-3423)
Pipe operator (|) could return wrong results. (MCOL-174)
operator could return wrong results. ()
Comparison of padded strings could provide incorrect results. ()
could fail when table name contained space and certain characters; not A-Z a-z 0-9 _ ()
DISTINCT could be performed in incorrect order relative to Window functions and UNION ()
cpimport outputs value truncation warning when read buffer (-b) is set to 1 ()
Cross-engine joins with query using DISTINCT could return NULL ()
Bulk write API writes were possible when writes were suspended. ()
Multi-column statements could produce incorrect results. ()
JOIN could significantly waste memory. ()
Memory leaks. ()
Plugin metadata was inconsistent. (, )
Cosmetic typo in postConfigure output. Output upon success is now MariaDB ColumnStore Install Successfully Completed, System is Active (MCOL-1598)
Performance of some queries, such as those containing UNION, may be worse than on ColumnStore 1.2.x.
Columnstore_commit_hash status variable added
Columnstore_version status variable added
columnstore_compression_type system variable added
columnstore_decimal_scale system variable added
columnstore_derived_handler system variable added
columnstore_diskjoin_bucketsize system variable added
columnstore_diskjoin_largesidelimit system variable added
columnstore_diskjoin_smallsidelimit system variable added
columnstore_double_for_decimal_math system variable added
columnstore_group_by_handler system variable added
columnstore_import_for_batchinsert_delimiter system variable added
columnstore_import_for_batchinsert_enclosed_by system variable added
columnstore_local_query system variable added
columnstore_orderby_threads system variable added
columnstore_ordered_only system variable added
columnstore_replication_slave system variable added
columnstore_select_handler system variable added
columnstore_string_scan_threshold system variable added
columnstore_stringtable_threshold system variable added
columnstore_um_mem_limit system variable added
columnstore_use_decimal_scale system variable added
columnstore_use_import_for_batchinsert system variable added
columnstore_varbin_always_hex system variable added
Columnstore ha_columnstore.so plugin added
COLUMNSTORE_COLUMNS information schema table added
COLUMNSTORE_EXTENTS information schema table added
COLUMNSTORE_FILES information schema table added
COLUMNSTORE_TABLES information schema table added
mysqld --columnstore-columns command-line option added
mysqld --columnstore-compression-type command-line option added
mysqld --columnstore-decimal-scale command-line option added
mysqld --columnstore-derived-handler command-line option added
mysqld --columnstore-diskjoin-bucketsize command-line option added
mysqld --columnstore-diskjoin-largesidelimit command-line option added
mysqld --columnstore-diskjoin-smallsidelimit command-line option added
mysqld --columnstore-double-for-decimal-math command-line option added
mysqld --columnstore-extents command-line option added
mysqld --columnstore-files command-line option added
mysqld --columnstore-group-by-handler command-line option added
mysqld --columnstore-import-for-batchinsert-delimiter command-line option added
mysqld --columnstore-import-for-batchinsert-enclosed-by command-line option added
mysqld --columnstore-local-query command-line option added
mysqld --columnstore-orderby-threads command-line option added
mysqld --columnstore-ordered-only command-line option added
mysqld --columnstore-replication-slave command-line option added
mysqld --columnstore-select-handler command-line option added
mysqld --columnstore-string-scan-threshold command-line option added
mysqld --columnstore-stringtable-threshold command-line option added
mysqld --columnstore-tables command-line option added
mysqld --columnstore-um-mem-limit command-line option added
mysqld --columnstore-use-decimal-scale command-line option added
mysqld --columnstore-use-import-for-batchinsert command-line option added
mysqld --columnstore-varbin-always-hex command-line option added
mysqld --columnstore command-line option added
In alignment to the MariaDB Corporation Engineering Policy, MariaDB ColumnStore 1.4.4 is provided for:
Red Hat Enterprise Linux 8
Red Hat Enterprise Linux 7
CentOS 8
CentOS 7
Ubuntu 20.04
Ubuntu 18.04
Ubuntu 16.04
Debian 10
Debian 9
SUSE Linux Enterprise Server 15
SUSE Linux Enterprise Server 12
Note: MariaDB Enterprise ColumnStore 1.4 is no longer supported. If you would like to deploy Enterprise ColumnStore, please use MariaDB Enterprise ColumnStore 5 or later. For installation and upgrade instructions, see "Deploy".
MCOL-392 - TIME data type is
MCOL-320 - TIME and DATETIME data types
MCOL-497 - Cross Engine Joins now support SSL connections
Improved DDL syntax support
- BOOL / BOOLEAN alias for TINYINT - with thanks to community contributor "tntnatbry"
- Backticks & reserved words now supported
- Non-alphanumeric table/column names now supported
- User Defined Aggregate / Window Functions now support multiple parameters.
- and are now supported.
- CREATE TABLE...LIKE
- A is now available which allows loading data directly from any server. This tool is included in the MariaDB ColumnStore Tools package
- support for bulk write SDK
Pentaho data adapter is now also available for Windows 10
MCOL-1322 - data corruption when setting NUMERIC columns to NULL through the python and C++ API
MCOL-1523 - OAM Process failover logic for DDLproc is incorrect - causing DDL to stop working
MCOL-1606 - PDI 8 - variable substitution doesn't work
MCOL-1648 - pymcsapi3 on Windows depends on the Python 3 release DLL it was compiled with
- support space names in columnstore table column names
- Change Windows mcsapi build to use libraries from external directory
- PDI plugin CI tests - add check with PDI 8
- javamcsapi - compatibility test fails if executed multiple times
- Test script for Win is searching for wrong named zip file
- Increase Gradle dependency resolution timeout to 5min
- Add OS information to Kettle zip file
- Add Windows suffix to kettle data adapter
- Saturated time() func handling is different to MariaDB
- Saturated addtime() func handling is different to MariaDB
- CS does not support reserved words as column names
- HOUR() function returns NULL when it should not
- Renaming a table in non-current database fails
- cpimport with down system say InfiniDB
- Column name can not start with numeric value
- data corruption when setting NUMERIC columns to NULL through the python and C++ API
- CS objects' identifiers doesn't support U+0000..U+007f even when quoted
- ColumnStore system logging not working after 1.1.4 ubuntu-16 install
- Scala connector won't compile in Ubuntu 18.04
- Create table statement doesn't allow usage of C style comments in it
- Forked server crashes in Item_ident::print() for a Temptable_field.
- Performance Schema crashes prepared statement
- Change Windows mcsapi build to use libraries from external directory
- Increase Gradle dependency resolution timeout to 5min
- BOOLEAN data type not supported
- support query of milli and micro second time parts
- TIME datatype is not supported
- support ssl connection in cross engine joins
- add distributed regression aggregate and window functions
- clean up engine repo cmake warnings
- CS does not support reserved words as table names
- support non alphanumeric characters for table and column names
- Disable Query Cache for ColumnStore
- Implement GROUP BY pushdown support
- DecomSvr should be removed
- Allow UDAnF to have multiple parameters defined.
- Remote CpImport
- make postConfigure default install non-distributed
- mcsapi Windows support
- Hardening Flags pt 2
- Merge
- Add time field support for PDI plugin
- Make the default installation option to separate instead of combined.
- ColumnStore to allow CREATE TABLE table_name LIKE ... Syntax
- mcsapi Windows - add needed Windows Redistributables to installer
- Informatica PowerCenter Bulk Write Connector
- Implement regr_sxx, regr_syy, regr_sxy and corr functions as UDAF
- Add mcsimport to PATH
- Investigate renewed in 10.3 CASE implementation.
- Include Windows library build into mcsapi
- TIME: cpimort saturates reserved NULL and empty indicator values incorrectly
- TIME: LDI saturates out-of-range values incorrectly
- TIME: Update saturates out-of-range values incorrectly
- Microsecond values are stored left-justified with trailing 0 padding
- SUBTIME() as a WHERE condition on TIME data type caused primProc to hang
- DAYNAME() and MONTHNAME() on TIME data type columns caused primProc to restart
- Some functions return non-matching results after data type TIME was added to the functions test suite
- Joiner array boundary bug
In addition, all bugs fixed in MariaDB ColumnStore 1.1.6 and earlier are implicitly included in this release.
The following procedure outlines upgrading a 1.1.6 ColumnStore install to 1.2.0:
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-1782 - UPDATE and DELETE reported incorrect affected row count
MCOL-1792 - mcsapi can incorrectly insert milliseconds
- length() on BLOB data generates an error
- cpimport cannot handle "true" keyword for boolean/numeric data types in cpimport
- mcimport can show a warning about column sizes during import
RPM, Debian, and binary packages are provided for the Linux distributions supported by MariaDB ColumnStore 1.2.0 Alpha version.
The supported OS for the Alpha version are CentOS 6, CentOS 7, Debian 8, Debian 9, RedHat 6, RedHat 7, SUSE 12, Ubuntu 16.04 and Ubuntu 18.04.
Packages can be downloaded here or can be installed from the repositories.
An Amazon AWS AMI Image is available for this release, please search for AMI name "MariaDB-ColumnStore-1.2.0". 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
Write Data API - Source code for Write Data API /SDK
MaxScale CDC and Kafka Data Adapters -
Release date: 21st February 2018
is a GA release of MariaDB ColumnStore. This is the fourth release of the MariaDB ColumnStore 1.1 series. This release of MariaDB ColumnStore provides improvements over the previous 1.1.2 GA release.
MariaDB ColumnStore 1.1.3 is a release.
For an overview of see
Please provide feedback in 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 or subscribe to mariadb-columnstore@googlegroups.com
Beta release of Apache Spark Adapter for integration of MariaDB ColumnStore utilizing the Spark SQL feature.
GA release of
GA release of
MCOL-1121 - The Kafka adapter has been made to work with more generic streams
- The base MariaDB server version is now which include several maintenance and security fixes.
MCOL-258 - Window function create is hidden
MCOL-436 - Alarms is being incorrect processed on local node
MCOL-782 - Non-recursive Common Table Expressions used in view caused an error
MCOL-927 - RPM packages for Centos 6.7 returned an libmariadb.so.3 loading error
- mysqld logs wrong columnstore version number
- UDAF incorrect error on some joins
- mysqld crashing on slave replication UMs
- tpcds query78 alternately fails and works with incorrect results
- cpimport failed with a "new extent FBO too high for current file error"
- Logic issue breaking multiple where conditions
- DDl/DML incorrect starts when active on um2 during a pm outage
- ERROR 2013 (HY000): Lost connection to MySQL server during query
- Server and Engine should use CPACK_DEBIAN_PACKAGE_SHLIBDEPS
- inconsistent library naming for JAVA write SDK
- postConfigure on debian 9.2 fails with libreadline.so.5 link error
- debian 9.2 cluster tester issues
- debian9 api python bindings built for python3 but installed in python2
- Post Configure reports incomplete name for script to run
- High concurrency can lock up PrimProc
- non-root install- getsystemdisk doesnt show any info
- Compression ratio miscalculation when there are uncompressed columns
- tupleconstantstep assert when query executed as view
- mcsapi packet stitching can fail
- mcsapi getTableLock not failing
- row_count() function always returns 0 for any engine
- cannot execute 2 subqueries with blob in select part
- ssh certificates aren't used in postConfigure nonDistributed installation with DataRedundancy between PMs enabled.
- ColumnStore API is missing dependencies in the documentation for the Debian installation
- crash with large writes on java binding of write sdk
- multi-node install fails, mysqld didnt startup in time
- After rollback() an active transaction is reported by mcsadmin shutdownSystem
- Set cpack deb minimum version to 3.4
- exemgr becomes non responsive
- Initialization of the Java Swig library within the parent class loader on package import
- mcsapi string->decimal conversion corruption for long and negative data
- non-root install - columnstoreAlias file not update and reference by postConfigure
- non-root install - post-install accidentally starts columnstore service
- Mysql replication master and slave both setup after a masternode failover
- pm1 failover testing - didnt leave a HOT_STANDBY ProcMgr on remainng node
- multiple mcsapi sessions use the same txnID
- change columnstore debian package name from cmake
- Small memory leak in mcsapi
- Bulk write API doesn't start new block for dictionary
- Use the threadpool automatic idle down facility
- postConfigure - option -c not working
- SystemCatalog Test fails
- 10Mio Row test fails, only 9988608 rows are written to ColumnStore
- SparkConnector runs out of memory for large datasets, JDBC can handle the datasets just fine
- empty result with "case .. when" with where condition and multiple parameter in "IN" clause
- non-root Log Rotation not working
- configAlarm error: Oam::setAlarmConfig: error opening file /usr/local/mariadb/columnstore/etc/AlarmConfig.xml: Permission denied
- Process ID of mysqld is missed in the output of mcsadmin getSystemInfo
- columnstoreRestore version check broken
- Let the Spark Connector use the native floating point datastructure
- columnstoreRestore does not restore correct config file
- columnstore_info procedures can only be used from within columnstore_info
- An aborted query during an aggregate will crash ExeMgr
- split character import issue
- mycnf config change request
- Funtcion/table to find out if ColumnStore instance (UM) is ready to process SQL queries against ColumnStore tables
- cluster tester enhancements - check for mysql password and mariadb-libs package
- Add automatic stack trace to ColumnStore binaries
- Basic Java example of cpimport which uses the columnstore API
- spark connector for publishing dataframe results using mcsapi to columnstore.
- Introduce benchmarks to test the performance with regards to jdbc
- Create a consistent naming for scala and python spark exporter
- Forward Bulk Write API C++ Exceptions to Java
- Forward Bulk Write API C++ Exceptions to Python
- MariaDB ColumnStore Package Repository
- ColumnStore Cluster Test tool - wording improvmenets
- Merge
- Clarifications for the Bulk Write SDK documentation
- Clarification for the Bulk Write SDK documentation
- Generic Kafka Data Adapter
- build api for both python 2 and 3
- support group install of ColumnStore
- package build of mariadb-columnstore-tools
- Merge
- Merge
In addition, all bugs fixed in MariaDB ColumnStore 1.1.2 and earlier are implicitly included in this release.
The following procedure outlines upgrading a 1.1.2 ColumnStore install to 1.1.3:
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-271 empty string values are treated as NULL. This means you cannot insert empty values into a NOT NULL string column.
MCOL-365: Log files created by load data infile remain in the bulk/data/log and /tmp directories. If storage is a concern these can safely be removed.
MCOL-540 : In a non root Ubuntu install with local query enabled, the PM servers crash and restart on table creation.
MCOL-624 :MariaDB 10.2 WF create MEDIAN, PERCENTILE_CONT and PERCENTILE_DISC Window functions. MariaDB ColumnStore 1.1 was rewritten to use the server parser code which does not support the percentile window functions. This will be added in a later release. A median function has been provided instead as part of the User Defined Aggregate Function framework that provides similar functionality or can be adapted to support percentiles other than 0.5.
:Create table caused primproc crashed for a specific configuration
:Implement ha_calpont_impl_rnd_pos. Sorting of long text columns may fail.
:Implement joins between CHAR/VARCHAR and INT columns. ColumnStore now fails more consistently on incompatible join types. Explicit type casts must be used if this error is hit.
: Some functions return "The maximum row size" error when TEXT/LONGTEXT is used in a table
: After adding two PMs with gluster, cpimport failed on newly added PMs. The system must be restarted after adding PM modules with data redundancy / gluster storage.
: A newly added user module didn't have MariaDB replication slave setup
: ColumnStore start/restart can return before system is ready
: post-install non-root has incorrect permissions for /etc/rc.local
: LD_LIBRARY_PATH not set correctly in centos6 non-root install
The current logging default generates full verbose debug logs. This can be controlled by making logging configuration changes as described .
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 .
RPM, Debian, and binary packages are provided for the Linux distributions supported by MariaDB ColumnStore 1.1.3 GA version.
The supported OS for the GA version are CentOS 6, CentOS 7, Debian 8, Debian 9, RedHat 6, RedHat 7, SUSE 12, and Ubuntu 16.0.4.
Packages can be downloaded here or can be installed from the repositories.
An Amazon AWS AMI Image is available for this release, please search for AMI name "MariaDB-ColumnStore-1.1.3". 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
Write Data API - Source code for Write Data API /SDK
MaxScale CDC and Kafka Data Adapters -
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.