MariaDB ColumnStore 25.10.0 Release Notes

This is the first release of the 25.10 release series, and Alpha release status. For that reason, this page doesn't comprise minor bug fixes or feature changes.

ColumnStore 25.10.0 works with MariaDB Enterprise Server 11.8.

Role in MariaDB Enterprise Platform 2026

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

  • New, simplified upgrade process

Features

Query Accelerator (Alpha)

Access your InnoDB data in real time by processing it in the ColumnStore engine. This allows you to run fast analytics on live data, without needing to maintain a pipeline or delayed/batched insert into ColumnStore. Parallel-execute your OLAP queries straight from your transactional data [MCOL-5999]

Read-Replica Nodes

ColumnStore can now horizontally scale up and down faster and with less effort than ever before. By using shared storage, additional compute focused on just query execution, you can independently scale compute and QPS without needing to reimport your data. Example:

mcs cluster node add --node $pm2 --read-replica

New Upgrades Architecture

The new upgrade architecture automates almost everything, saving time and reducing risks. New pre- and post-upgrade checks keep your cluster safe [MCOL-5989]

New Operating System Support

• RHEL 10

• Debian 13 "Trixie"

New quality of life cpimport headers -e all and -L "/tmp/failed_records.out" options

• -e all

  • Now you can skip all errors when importing records similar to 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.

New log bundling, backup & restore orchestration via CMAPI

• mcs review --help

  • No longer do you need to download our supports external script for log bundling as cmapi includes this on every install. This will make it easier and quicker to bundle your logs and run other common checks. External scripts for log bundling aren't required anymore, because CMAPI includes log bundling. Example: mcs review --logs

• 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

Notable Items

• 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 [MCOL-5250]

Can result in hang or crash

• Post upgrade to 23.10.4, some of the queries giving different set of results upon executing multiple times [MCOL-6106]

• Extremely large primloc logs generated after upgrade from 23.10.3 to 23.10.4 [MCOL-6100]

• Deactivate_only logic is always enabled on node removal in CMAPI [MCOL-6105]

• Selinux rules needed to enable columnstore for rhel 10 [MCOL-5825]

• 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]

Related to performance

• Added ORDER BY and LIMIT/OFFSET processing for UNION queries. Handle UNION pushdown edge case that triggers slow table mode processing [MCOL-5756]

• Read-replica Columnstore nodes v1 [MCOL-5861]

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}