The Ultimate Guide to High Availability with MariaDB

MariaDB ColumnStore 1.0.5 Release Candidate Release Notes

You are viewing an old version of this article. View the current version here.

Release date: 22nd November 2016

MariaDB ColumnStore 1.0.5 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 Candidate release.

Do not use Release Candidate releases on production systems!

For an overview of MariaDB ColumnStore see MariaDB ColumnStore Architectural Overview

Please provide feedback in JIRA for anything that is not working as expected so that we can fix it before we make the release available for the larger community. For general "how to questions" ask questions here or subscribe to [email protected]

Notable Changes

  • 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 documentation for further details.
  • An install for Debian 8.6 is now available.

Bugs and Issues Fixed

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.
  • MCOL-129 - INSERTIONS are lost, no ERROR reported for out-of-range values in STRICT mode
  • MCOL-218 - DROP DATABASE on a database with all empty tables is not accepted
  • MCOL-260 - update two tables with a subquery fails
  • MCOL-263 - With suspendDatabaseWrite enabled, LDI return an incorrect msg
  • MCOL-273 - During restart, ProcessManager sometimes generates a warning
  • MCOL-278 - drop table if exists creates error if table doesn't exist and schema out of synch
  • MCOL-309 - Support method to report on data set size
  • MCOL-334 - Bad NULL match in view subquery
  • MCOL-350 - can't select date value of 0000-00-00
  • MCOL-352 - substr() on view returns NULL sometimes
  • MCOL-361 - table mode 0 and 2 has bad result
  • MCOL-370 - enableLog / disableLog don't work
  • MCOL-372 - dbrm-worker node continuing issues socket read error log
  • MCOL-385 - 10.1.19 Merge
  • MCOL-386 - postConfigure should show cause of write error.
  • MCOL-387 - releasenum gets messed up when not hard set
  • MCOL-398 - remove the restriction in postConfigure for UM memory at 16G
  • MCOL-404 - non-root install fails on centos7

Upgrade

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.

Known Issues and Limitations

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
  • 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.
  • The current logging default generates full verbose debug logs. This can be controlled by making logging configuration changes as described here.
  • While Millisecond and Microsecond storage is supported for datetime, time and timestamp columns, at this time the query results cannot return millisecond and microseconds.
  • UTF-8 Limitation
    • UTF-8 must be declared at the table level if the instance has been set up with a UTF-8 profile. Tables created with a non-matching character set will yield indeterminate results.
    • Viewing SQL output should be done using client software that supports UTF-8 character sets.
    • UTF-8 characters are not supported in object names.
  • Known security issues and fixes are documented here.

Documentation

MariaDB ColumnStore Documentation

Packaging

RPM 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

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

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.