Release Notes for MariaDB Enterprise ColumnStore 22.08.8

When ColumnStore is configured to use S3-compatible storage, if the endpoint and region parameters in /etc/columnstore/storagemanager.cnf do not refer to the same region where bucket is located, ColumnStore fails to send data to cloud storage, but does not detect the failure. (MCOL-5177)

• In previous releases, the endpoint would send ColumnStore an HTTP 301 status code to indicate a failure, but ColumnStore would incorrectly treat it as a success.

• Starting with this release, ColumnStore correctly identifies the failure and raises an error message:

  S3Storage::putObject(): Bucket location not match provided endpoint:, bucket = BUCKET, endpoint = ENDPOINT.
  

When processing a hash join, ExeMgr can crash with a SIGABRT. (MCOL-5265)

When a SELECT statement calls SUM(COLUMN=VALUE), the statement fails with an unclear error message. (MCOL-603)

• In previous releases, the following error is raised:

  ERROR 1815 (HY000): Internal error: std::bad_typeid
  

• Starting with this release, the following error is raised:

  ERROR 1178 (42000): The storage engine for the table doesn't support MCS-2027: Non supported item in aggregate function SUM(COLUMN=VALUE).
  

When the ANALYZE statement is executed with a SQL statement as an argument, ColumnStore can return an error. (MCOL-1170)

• In previous releases, the following error is sometimes raised:

  ERROR 1815 (HY000): Internal error: Unknown error
  

• Starting with this release, an error should not be raised, and the execution plan should be printed:

  ANALYZE SELECT * FROM t1 WHERE c1 = 1;
  

  +------+---------------+-------+------+---------------+------+---------+------+------+--------+----------+------------+-------+
  | id   | select_type   | table | type | possible_keys | key  | key_len | ref  | rows | r_rows | filtered | r_filtered | Extra |
  +------+---------------+-------+------+---------------+------+---------+------+------+--------+----------+------------+-------+
  |    1 | PUSHED SELECT | NULL  | NULL | NULL          | NULL | NULL    | NULL | NULL | NULL   |     NULL |       NULL | NULL  |
  +------+---------------+-------+------+---------------+------+---------+------+------+--------+----------+------------+-------+
  

When a column is added to a table on a primary node with multi-node ColumnStore, ColumnStore tries to add the new column to the table twice on the replica nodes, which causes a replication failure. (MCOL-5000)

• In previous releases, when replication failed, messages like the following appear in the MariaDB error log:

  [ERROR] Slave SQL: Error 'Got error 1815 "Unknown error 1815" from storage engine ColumnStore' on query. Default database: 'db1'. Query: 'ALTER TABLE t1 ADD COLUMN (col2 varchar(100))', Gtid GTID_POS, Internal MariaDB error code: 1030
  [Warning] Slave: Got error 1815 "Unknown error 1815" from storage engine ColumnStore Error_code: 1030
  [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'LOG_FILE' position LOG_POS; GTID position 'GTID_POS'
  

• Starting with this release, ColumnStore only adds the new column to the table once on the replica nodes, so the replication failure does not occur.

When querytstats is enabled, if a query contains a LEFT JOIN and the ON clause contains the LOWER() function, an error is written to the ColumnStore log. (MCOL-5223)

• In previous releases, the following error is written to the ColumnStore log:

  1e3afaf1eaef Calpont[135]: 37.906020 |0|0|0| E 00 CAL0000: /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.6.8/storage/columnstore/columnstore/dbcon/joblist/tuplehashjoin.cpp@1095: assertion 'idlsz > 1' failed
  

• Starting with this release, the query can be executed without raising an error.

When the TRUNCATE() function is called with a CHAR or VARCHAR column that contains numeric characters, an incorrect value is returned. (MCOL-5248)

When multi-node ColumnStore is configured to use shared local storage, replica nodes can overwrite their local copies of the extent map files multiple times during shutdown. (MCOL-5302)

When columnstore_use_import_for_batchinsert=ON is set on multi-node ColumnStore, INSERT INTO .. SELECT statements in a transaction report that rows were inserted, even though no rows are inserted. (MCOL-5367)

When ExeMgr finishes serving a request from MariaDB Server, ExeMgr's TCP connection can remain open, and its thread can continue running, which can cause ColumnStore to use more resources than required. (MCOL-5384)