MariaDB ColumnStore 1.1.1 Release Candidate Release Notes

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 .