Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Release notes for MariaDB ColumnStore 1.1
Release date: 21st November 2017
MariaDB ColumnStore 1.1.2 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 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 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.
- self join cte queries from tpcds alternately fail with parsing error and succeed but with incorrect results
- System in DBRM_READ_ONLY mode after Non-parent PM recovery under DataRedundancy
- The addmodule command reported an invalid password error if cluster on the new module is not running
- postConfigure on a DataRed setup should exiting when system install prompt is answered 'n'
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.
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.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
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 .
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: 19th June 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.4 GA release.
MariaDB ColumnStore 1.1.5 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
MCOL-998 - MySQL replication is not replicating after installation
MCOL-1008 - LDI and INSERT...SELECT causes mysqld to crash with long VARCHAR entries
MCOL-1009 - MCS Replication setup failure - mysqld failed to restart
MCOL-1010 - Debian 9 package: postConfigure failed to create /etc/rc.d/rc.local file
MCOL-1014 - Replication setup failed when using ssh key and schema sync enabled
MCOL-1016 - information_schema.columnstore_extents data_size calculation incorrect
MCOL-1020 - On ovh data center servers, postConfigure crashed on upgrade
MCOL-1021 - Dictionary deduplication cache is not working correctly
MCOL-1024 - postConfigure reported system catalog creation error but database continue to work
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-912 : 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.
MCOL-1083 : 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 .
MaxScale CDC and Kafka Data Adapters - Source Code for data adapters
MCOL-1412 - Ubuntu 18.04 is supported from this release onwards.
MCOL-1197 - CPIMPORT fails and Abandoned when data row is too BIG to Handle
MCOL-1229 - IS.columnstore_columns crashes when DDL is simultaneously executing
MCOL-1261 - mcsapi Python wrapper breaks on out of source builds
MCOL-1321 - bulk write sdk python bindings does not support status out param in setColumn
- A restriction for allowed length of the table and column names is not implemented
- ExeMgr failes to process SELECT with any field preceding UDAF functor.
- 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
- Spark connector does not allow NULL values
- Spark connector doesn't handle null values
- Network Error incorrect handled, Amazon DBROOT detach failed, but dbroot still was reassigned
- ColumnStore system logging not working after 1.1.4 ubuntu-16 install
- Couldn't use reserved words in idents even with quotes(backport from develop)
- SUBSTRING_INDEX returns NULL when the number parameter is negative
- kafka avro adapter install avro library issues
- VARCHAR returning NULL when StringStore memory limit exceeded
- update pdi data adapter to use explicit mcsapi version numbers
- Trailing whitespace in CHAR/VARCHAR break string matches - Revisited
- Mysqld PID is missed in the output of mcsadmin getSystemInfo
- Cannot create pv_facts table in develop
- Columnstore table unable to accept writes after thousands of commits via Bulk SDK
- CDC Connector v2.2.5-1 unable to connect to MaxScale
- rename the data-adapter kettle package to match the others
- mcsapi's dataconvert-decimal fails for Ubuntu 18.04
- mariadb-columnstore-kafka-adapters has been deprecated - remove from building
- Build for Kettle adapter is not created
- Columnstore provided udf median()/avg_mode() not working
- Pentaho Data Integration / Kettle - Bulk API Java Binding
- Spark connector - support different ColumnStore configurations
- ColumnStore Data-Adapters needs a top level cmake for building all Data-Adapters
- CREATE table STATEMENT from Spark Dataframe structure
- Update mariadb-columnstore-api package names to amd64 in make file for Debian/Ubuntu
- Backport Ubuntu 18.04 support to 1.1
- Merge into 1.1
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.
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
: 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 .
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 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.5". 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: 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
MariaDB ColumnStore 1.1.6 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 GA release.
For an overview of MariaDB ColumnStore see
Please provide feedback in JIRA for anything that is not working as expected so that we can fix it before we make the release available for the larger community. For general "how to questions" ask questions here or subscribe to mariadb-columnstore@googlegroups.com
- The base MariaDB server version is now which include several maintenance and security fixes.
- MariaDB's slow query log only logging vtable information
- Race condition in FIFO buffer
- NOT with null safe operator fails
- mcsapi BadUsage.AssertTableLock test creates phantom transaction
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.
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.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 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.6". 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: 18th September 2017
MariaDB ColumnStore 1.1.0 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 Beta release.
Do not use beta releases on production systems!
For an overview of MariaDB ColumnStore see
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.
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
- Query Failed after a redistributeDB while ddl/dml/queries were active
- TEXT and BLOB data types are not supported
- replace drizzle with maria client library
- switch to using os distribution version of snappy
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.
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.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
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 .
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 -
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-1301 - mcsapi won't compile with Python3 in Debug mode in CentOS 7
MCOL-1421 - test200 needs tuning
MCOL-1445 - mcsapi Java test fails on Ubuntu 18.04 and Java 10
MCOL-1453 - mcsapi doesn't detect when WriteEngineServer has gone away
MCOL-1468 - CDC adapter: mxs_adapter doesn't measure transaction insert time as expected
MCOL-1472 - where does not properly evaluate case when case when on varchar columns
MCOL-1474 - PriorityThreadPool can crash
MCOL-1490 - Data-Adapter package has different names for RPM and DEB
MCOL-1491 - auth_pam.so plugin missing from server package
MCOL-1498 - Installation failed in Replication Distribution command
MCOL-1525 - Non-root Install - core dumps not working
MCOL-1527 - Incorrect 0 row(s) affected on delete with cross engine join
MCOL-1531 - ColumnStore fails to make inner join if using CASE in predicate.
MCOL-1535 - Case when~ vs case ~ when ~
MCOL-1545 - Compiler error in GCC 8.1
MCOL-1566 - mcsapi documentation build issue in CentOS 7
MCOL-1579 - ColumnStore as root crashes processes using shm
MCOL-1588 - javamcsapi ColumnStoreBulkInsert can't manually be garbage collected
MCOL-1594 - mxs_adapter requires -t to gracefully exit
MCOL-1595 - mxs_adapter state file is stored in the current directory
MCOL-1605 - sendAlarmReport error: InetStreamSocket::connect: connect() error: Connection timed
MCOL-1612 - python spark connector - broken
MCOL-1635 - insert into select crashes for a BLOB column
MCOL-1655 - Yacc debug hard coded on
MCOL-1664 - data-adatper centos7 package rename not executed
MCOL-1675 - Incorrect HWM calculation if the table's first column width > 1
MCOL-1684 - Performance Schema crashes prepared statement
MCOL-1705 - check hardcoded uses of root user for mysql
MCOL-1330 - Make ColumnStore work under valgrind
MCOL-1376 - Support Ubuntu 18.04
MCOL-1475 - Improve cross engine error handling
MCOL-1484 - Use condition pushdown in I_S tables
MCOL-1521 - Java - mcsapi - introduce new function getJavaMcsapiVersion()
MCOL-1524 - Backward / Forward compatibility test for javamcsapi and mcsapi
MCOL-1551 - Ability to configure ColumnStore to use domain names instead of IP addresses
MCOL-1591 - add UMASK check to ColumnStore Cluster Tester script
MCOL-1596 - mxs_adapter multi-table support
MCOL-1661 - Transform CDC events into UPDATE and DELETE statements
MCOL-1145 - One step configuration of Single Server Node
MCOL-1146 - One step configuration of Multi Server Node
MCOL-1439 - Documentation for Python API missing
MCOL-1615 - Merge MariaDB 10.2.17
MCOL-1617 - remove generated build doc from mcsapi in favor of its Readme.md in Github
MCOL-1646 - Update ColumnStore docs for 18.04
MCOL-1496 - Joiner array boundary bug
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-1654: 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 .
MaxScale CDC and Kafka Data Adapters - Source Code for data adapters
.
MariaDB Server .
Built-in data redundancy using GlusterFS integration for installations that use local disks for data storage on PMs. Please refer to Preparing ColumnStore Installation for using GlusterFS with MariaDB ColumnStore.
Several performance improvements in string handling, memory utilization and general area.
MCOL-356 - BLOB data type not supported
MCOL-377 - columnstore queries show as vtable query rather than original query in audit log
MCOL-397 - binary package install doesnt check for package dependencies
MCOL-463 : gluster storage option in installer fails with an error.
MCOL-468 - update default replication configuration
MCOL-480 - warning error reported after upgrade to 1.0.6
MCOL-507 - More performance improvements to ExeMgr
MCOL-511 - native write data api
MCOL-513 - analyze and implement thread pools and memory buffers for performance optimization
MCOL-518 - backup (cold) and restore tool
MCOL-519 - productize glusterfs support and add tools to automate
MCOL-522 - support pre-installed software in postConfigure and addModule - phase I
MCOL-523 - support user defined aggregate functions
MCOL-534 - postCfg upgrade output refers to calpont
MCOL-550 - Possible mem leak and crash in columnstore's mysqld
MCOL-553 - "Too many open files" errors during DBT3 performance test
MCOL-561 - Can't create view by using ColumnStore's windowing funcion SQL
MCOL-574 - Cross Engine step tries to use a bad UDS path for localhost
MCOL-579 - Enabled harderning compile flags
MCOL-622 - MariaDB 10.2 create front end for "VAR_SAMP" window function
MCOL-623 - MariaDB 10.2 create "STDDEV_SAMP" Windows function
MCOL-628 - getSystemResourceUsage doesnt work on non-root install
MCOL-636 - Performance improvement with string handling
MCOL-642 - Add BLOB/TEXT detection
MCOL-663 - Restarting installation fails if installed on secondary interface
MCOL-664 - TEXT columns need to support the same functions as VARCHAR
MCOL-675 - calsettrace(1) can cause a mysqld crash
MCOL-677 - Columnstore executes join on incompatible types
MCOL-686 - Using BETWEEN together with date functions in WHERE clause 100x slower than InfiniDB
MCOL-702 - multi node package install with non login su won't start
MCOL-703 - postConfigure should check for local rpm / bins existing
MCOL-729 - Columnstore Cluster Test Tool - add check for mariadb-libs base install
MCOL-787 - run command to create system tables after startsystem
MCOL-799 - INSERT...SELECT with window functions fail
MCOL-819 - mysqld not shutdown by shutdownsystem commands, sometimes
MCOL-833 - could not open file for OID after a outage recover from pm2 PrimProc
MCOL-887 - Merge MariaDB 10.2.8
MCOL-892 - 1.0.11 upgrade failed when base directory is nfs mounted
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-783 : Recursive Common Table Expressions caused mysqld to crash
MCOL-895 : INSERT after ALTER TABLE can corrupt HWM
MCOL-912 : 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.
MCOL-916 : 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.
MCOL-926 : 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 .
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 -
Release date: 3rd November 2017
MariaDB ColumnStore 1.1.1 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 Candidate release.
Do not use Release Candidate 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
MariaDB ColumnStore 1.1.1 is based on MariaDB Server 10.2.10
Java and Python bindings are available for the Write Data API
- Unexpected results in cross engine join
- Installation of MCS updates the root .bashrc file
- make the remote server install scripts run faster by checking for ssh/scp return codes
- Recursive Common Table Expressions caused mysqld to crash
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.
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.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
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 .
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 -
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
MCOL-786 - redistribute remove moved data from removed node to one node
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-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-913 - DistributeConfigFile Failed messages after adding modules
MCOL-914 - Warning messages for the RemoveModule command should be improved
MCOL-915 - Improve the output from the RemoveModule command
MCOL-916 - Gluster failover: Stack did not recover completely after PM1 reboot
MCOL-926 - UDAF returns null for 2nd or more applications against same column
MCOL-928 - postConfigure is not detecting glusterfs on Debian9.1 for non-root user
MCOL-929 - switchparentoammodule cores when pm2 is active on a 1um/2pm Data Redundancy system
MCOL-938 - columnstore replication failover from master updates server-id
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-946 - migrate to swig for mcsapi python binding
MCOL-951 - tpcds query 17 fails with invalid colum width
MCOL-959 - invalid LD_LIBRARY_PATH for non root install
MCOL-963 - self join cte queries from tpcds alternately fail with parsing error and succeed but with incorrect results
MCOL-965 - group_contact with order by on joined table causes error
MCOL-971 - 1.0 to 1.1 non-root upgrade issue - problem shows after a reboot, still using 1.0 ENV variables
MCOL-972 - PmMaxMemorySmallSide configuration value not carried forward in upgrade
MCOL-973 - ArithmaticColumn parsing can cause crash
MCOL-979 - Crash with LEAD function in ColumnStore with 'char' field type
MCOL-982 - Merge MariaDB 10.2.9 into ColumnStore
MCOL-984 - Error 1815 after several executions of example/basic_bulk_insert having SMALLINT in t1
MCOL-988 - 1um/2pm DataRep system starting up without a ProcessManager in HOT_STANDBY state
MCOL-990 - provide a resetRow method
MCOL-992 - java binding for mcsapi
MCOL-1000 - Merge MariaDB 10.2.10
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-912 : 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 .
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.