MariaDB ColumnStore 1.1.0 Beta Release Notes

Release date: 18th September 2017

MariaDB ColumnStore 1.1.0arrow-up-right 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 ColumnStorearrow-up-right see MariaDB ColumnStore Architectural Overview

New Features

  1. MariaDB ColumnStore 1.1.0 is based on MariaDB Server 10.2.8

  2. The Window functions have been re-implemented with MariaDB Server 10.2.8 code.

  3. Text and Blob Data Types.

  4. MariaDB Server Audit Plugin Integration.

  5. Built-in data redundancy using GlusterFS integration for installations that use local disks for data storage on PMs. Please refer to Preparing ColumnStore Installationarrow-up-right for using GlusterFS with MariaDB ColumnStore.

  6. Several performance improvements in string handling, memory utilization and general area.

Please provide feedback in JIRAarrow-up-right 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

Bugs and issues fixed

In addition, all bugs fixed in MariaDB ColumnStore 1.0.11 and earlier are implicitly included in this release.

Upgrade

Multi version upgrades are not supported, please upgrade versions prior to 1.0.11 before upgrading to 1.1.0:

Known issues and limitations

There are a number bugs and known limitations within this version of MariaDB ColumnStore, the most serious of these are listed below.

  • MCOL-271arrow-up-right empty string values are treated as NULL. This means you cannot insert empty values into a NOT NULL string column.

  • MCOL-365arrow-up-right: 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-540arrow-up-right : In a non root Ubuntu install with local query enabled, the PM servers crash and restart on table creation.

  • MCOL-624arrow-up-right :MariaDB 10.2 WF create MEDIAN, PERCENTILE_CONT and PERCENTILE_DISC Window functions. MariaDB ColumnStore 1.1 was rewritten to use the MariaDB 10.2 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.

  • MCOL-631arrow-up-right :Create table caused primproc crashed for a specific configuration

  • MCOL-643arrow-up-right :Implement ha_calpont_impl_rnd_pos. Sorting of long text columns may fail.

  • MCOL-695arrow-up-right :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-713arrow-up-right : Some functions return "The maximum row size" error when TEXT/LONGTEXT is used in a table

  • MCOL-783arrow-up-right : Recursive Common Table Expressions caused mysqld to crash

  • MCOL-895arrow-up-right : INSERT after ALTER TABLE can corrupt HWM

  • MCOL-912arrow-up-right : 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-916arrow-up-right : 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-926arrow-up-right : 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 here.

  • While Millisecond and Microsecond storage is supported for datetime, time and timestamp columns, at this time the query results cannot return millisecond and microseconds.

  • UTF-8 Limitation

    • UTF-8 must be declared at the table level if the instance has been set up with a UTF-8 profile. Tables created with a non-matching character set will yield indeterminate results.

    • Viewing SQL output should be done using client software that supports UTF-8 character sets.

    • UTF-8 characters are not supported in object names.

  • Known security issues and fixes are documented here.

Documentation

MariaDB ColumnStore Documentationarrow-up-right

Packaging

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 herearrow-up-right

  • 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 herearrow-up-right.

  • Certified to run in Google Cloud Environment in the GA OSs.

Source code

The source code of MariaDB ColumnStore is tagged at GitHub with a tag, which is identical with the version of MariaDB ColumnStore. For instance, the tag of version X.Y.Z of MariaDB ColumnStore is columnstore-X.Y.Z. Further, master always refers to the latest released non-beta version.

The source code is available at these locations

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

spinner

Last updated

Was this helpful?