Release Notes for MariaDB Enterprise ColumnStore 1.5.3

MariaDB Enterprise ColumnStore is a columnar storage engine included with MariaDB Enterprise Server. This is the first release in the Enterprise ColumnStore 1.5 series, and marks the first major release since integration with MariaDB Enterprise Server.

This release is focused on architectural change, product quality, and improved alignment to MariaDB Enterprise Server.

This release of MariaDB Enterprise ColumnStore is included with MariaDB Enterprise Server 10.5.4-2.

This release is of gamma maturity.

MariaDB Enterprise ColumnStore 1.5.3 was released on 2020-07-16.

Notable Changes

  • Comprehensive rewrite of installation, administration, cluster management, and failover logic. (MCOL-3836)

  • Simplified installation:

  • Simplified administration:

    • mcsadmin has been removed. Instead, Enterprise ColumnStore 1.5 uses systemd for administration of single-node and multi-node deployments, and it also adds a new REST API for administration of multi-node deployments.

    • The new systemd service called mariadb-columnstore is used to manage ColumnStore's processes.

    • The new REST API is used to manage multi-node ColumnStore deployments.

    • The new REST API provides an interface for MariaDB MaxScale 2.5 to orchestrate the multi-node Enterprise ColumnStore deployment.

    • See OAM Replacement for more details.

  • Support for standard MariaDB Enterprise Server collation and character sets. (MCOL-337)

  • Improved performance for REGR_* functions. (MCOL-3837)

  • This release was the source for fixes previously backported to ColumnStore 1.4.4.

  • This release includes correction of regressions present in ColumnStore 1.4.4 vs pre-integration.

  • Fixes for defects in tiered storage and S3-compatible object storage.

Bugs Fixed

Can result in crashes, hangs, stalls

  • mariadbd will abort if Columnstore.xml is missing. (MCOL-3853)

  • Intermittent crash of cpimport in some complicated workflows. (MCOL-3865)

  • Exceeding thread limits will cause queries against S3-compatible object storage to hang. (MCOL-3858)

  • Error was not properly returned when a COMMIT or ROLLBACK failed, triggering an assertion. (MCOL-4124)

Can result in unexpected behavior

  • mcs-storagemanager attempted startup when not needed. (MCOL-4151)

  • COUNT(DISTINCT) on more than one column produces an error. (MCOL-3857)

  • REVERSE() function does not work with non-Latin characters. (MCOL-2221)

  • Multi-table DROP IF EXISTS generates an error instead of a warning. (MCOL-4164)

  • UPDATE with SELECT returning nulls may produce wrong answer. (MCOL-4116)

  • rand() calls with the same seed value return different results. (MCOL-3760)

  • Attempt to INSERT a TINYINT with an out-of-range value can generate a spurious error message. (MCOL-3777)

  • A query containing a Common Table Expression (CTE) can return the wrong error message, that a field is not in the GROUP BY clause even if it is. (MCOL-3782)

  • Complex queries using UNION can return the wrong error message, table not found. (MCOL-3828)

  • COUNT(NULL) doesn't work as a window function. (MCOL-3839)

  • The wrong error message is given when a function not supported by ColumnStore is used inside a function that is supported by ColumnStore. (MCOL-3924)

  • microsecond support for from_unixtime

  • INSERT after a LOAD DATA LOCAL INFILE in a transaction may silently fail. (MCOL-4002)

  • IN clause in WHERE could be evaluated improperly. (MCOL-2096)

  • A spurious "file not found" error message can occur when query, truncate, and cpimport collided. (MCOL-3521)

  • Internal error: IDB-2035 can occur with BIT_OR function in projection and subquery in FROM. (MCOL-3356)

  • Multi-byte characters mishandled in DML export to cpimport-1.5. (MCOL-4017)

  • GROUP_CONCAT() with ORDER BY and long doubles may fail. (MCOL-3904)

  • CONV() returned less characters in the resulting string. (MCOL-3596)

  • MODA() produces memory leak. (MCOL-4042)

  • Memory leaks. (MCOL-4043) (MCOL-3934)

  • EXPLAIN generates error on every other (alternating) execution. (MCOL-3860)

  • Renaming a table causes schema to become out of sync between MariaDB Server catalog and ColumnStore. (MCOL-3859)

  • Incorrect COUNT(*) with a complex view. (MCOL-3813)

Known Issues

  • Built-in SQL functions do not work in ColumnStore when sql_mode=ORACLE (MCOL-4044)

Interface Changes

None.

Platforms

In alignment to the MariaDB Corporation Engineering Policy, MariaDB ColumnStore 1.5.4 is provided for:

  • Red Hat Enterprise Linux 8

  • Red Hat Enterprise Linux 7

  • CentOS 8

  • CentOS 7

  • Ubuntu 20.04

  • Ubuntu 18.04

  • Ubuntu 16.04

  • Debian 10

  • Debian 9

  • SUSE Linux Enterprise Server 15

  • SUSE Linux Enterprise Server 12

Important

MariaDB Enterprise ColumnStore 1.5 has been superseded by MariaDB Enterprise ColumnStore 5.4 in MariaDB Enterprise Server 10.5. For installation and upgrade instructions, see Deploy MariaDB ColumnStore 5.4 with MariaDB Enterprise Server 10.5.