Release Notes for MariaDB Enterprise Server 10.4.22-14

Overview

MariaDB Enterprise Server 10.4.22-14 is a maintenance release of MariaDB Enterprise Server 10.4. This release includes a variety of fixes.

MariaDB Enterprise Server 10.4.22-14 was released on 2021-12-13.

Fixed Security Vulnerabilities

CVE (with cve.mitre.org link)

CVSS base score

CVE-2021-35604

5.5

CVE-2021-46662

5.5

CVE-2021-46667

7.5

Notable Changes

  • Enterprise Spider no longer enables pushdown of UDFs and Stored Functions to the Data Node by default:

    • The default value of spider_use_pushdown_udf has changed from -1 to 0

    • In previous releases, Enterprise Spider pushed UDFs and Stored Functions down to the Data Node by default, which could cause query results to be inconsistent.

    • Starting with this release, all UDFs and stored functions are evaluated on the Spider Node by default. If desired, pushdown of UDFs and Stored Functions can be explicitly enabled by setting spider_use_pushdown_udf=1. Testing is recommended to confirm that query results are consistent. (MDEV-26545)

  • Performance Schema tables provide descriptions of each column in the COMMENT column option. (MDEV-25325)

Issues Fixed

Can result in a hang or crash:

  • InnoDB causes server crash when a table is converted from utf8mb3 to utf8mb4 (MDEV-25951)

  • Server crashes when a table uses a sequence as a column default (DEFAULT NEXT_VALUE(my_seq)) and the table is used concurrently by both a prepared statement and a normal statement. (MDEV-22785)

  • When enabling MariaDB Enterprise Audit, server crash can occur. (MENT-1307)

  • MariaDB Enterprise Audit occasionally hangs when rotating logs. (MENT-1339)

  • InnoDB sometimes causes server crash during ALTER TABLE .. IMPORT TABLESPACE when the imported tablespace contains columns that have been instantly reordered or dropped. The MariaDB error log contains the following error message:

    Schema mismatch (Index field name newcol doesn't match tablespace metadata field name name for field position… (MDEV-26621) (MDEV-18543)

  • MariaDB Enterprise Cluster can crash due to an incorrect conflict resolution on multi-master setup. (MDEV-25368) (MDEV-25114)

  • MariaDB Enterprise Cluster hangs while it is executing DELETE FROM mysql.wsrep_cluster, which can be seen in the process list. (MDEV-26760) (MDEV-25883)

Can result in unexpected behavior

  • Password validation plugins (including simple_password_check) cause a user's existing password hash to be removed from the server's in-memory privilege cache when the user tries to change their password to an invalid password. (MDEV-26650)

  • If an INVISIBLE column has a computed default value, an INSERT statement that doesn't specify a value for the column causes the default value to be ignored. (MDEV-25891)

  • In packets sent from the server, a column's "Original Name" field can contain the column's alias instead of original name of the column. This metadata mismatch can cause MariaDB Connectors to raise an exception. (MDEV-23519)

  • When using MariaDB Enterprise Cluster and MariaDB Replication with GTID between two clusters, MariaDB Replication between the clusters is not working. Also, system variable wsrep_gtid_seq_no is missing. (MENT-1324)

  • With MariaDB Enterprise Cluster, a TRUNCATE on a table with a Foreign Key Constraint is not replicated to other nodes. (MDEV-26053)

Install and Upgrade

  • On CentOS 7, auth_pam_tool has incorrect permissions. (MDEV-26380)

Platforms

In alignment to the enterprise lifecycle, MariaDB Enterprise Server 10.4.22-14 is provided for:

  • CentOS 7 (x86_64)

  • CentOS 8 (x86_64 / ARM64)

  • Debian 9 (x86_64 / ARM64)

  • Debian 10 (x86_64 / ARM64)

  • Microsoft Windows (x86_64)

  • Red Hat Enterprise Linux 7 (x86_64)

  • Red Hat Enterprise Linux 8 (x86_64 / ARM64)

  • SUSE Linux Enterprise Server 12 (x86_64)

  • SUSE Linux Enterprise Server 15 (x86_64 / ARM64)

  • Ubuntu 18.04 (x86_64 / ARM64)

  • Ubuntu 20.04 (x86_64 / ARM64)

Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see "MariaDB Corporation Engineering Policies".