From April 2024, the release notes include the following changes:
The release notes for product versions are added. For example, features such as columnar storage engines and compatibility with MySQL 8.0 are added in V2.4.0.
The release notes are categorized into release notes for compute nodes, data nodes, Change Data Capture (CDC) nodes, and columnar nodes.
The component version number consists of a three-digit version number and the release date (replacing the original buildNumber).
Sample product versions: polardb-2.4.0_5.4.19-20240426_xcluster5.4.19-20240412 (MySQL 5.7-compatible) and polardb-2.4.0_5.4.19-20240426_xcluster8.4.19-20240430 (MySQL 8.0-compatible)
polardb-2.4.0: the product version.
5.4.19-20240426: the component version on the compute nodes. 5.4.19 is the three-digit version number, and 20240426 indicates the release date.
xcluster5.4.19-20240412: the component version on the data nodes. 5.4.19 is the three-digit version number (MySQL 5.7-compatible), and 20240412 indicates the release date.
xcluster8.4.19-20240430: the component version on the data nodes. 8.4.19 is the three-digit version number (MySQL 8.0-compatible), and 20240430 indicates the release date.
Release date: 2024-04-18
Product version: polardb-V2.4.0
Category | Description |
New feature and feature optimization | A cost-effective specification is introduced for read-only columnar nodes. You can use this specification together with different specifications of row store nodes to ensure support for scenarios that involve mixed workloads. |
A global database network (GDN) can be connected, which provides a high-performance, stable, and reliable cross-cloud deployment solution and significantly enhances the performance and reliability of master-replica replication. | |
In-Memory Column Indexes (IMCIs) can be created, and the query optimizer is optimized. This significantly improves the efficiency of complex queries. | |
Fully compatible with MySQL 8.0 protocols and syntax. | |
Feature optimization | The online alteration of column types is optimized to improve stability, and the time required for the alteration is reduced. |
DDL operations, such as adding or removing columns, adding or removing indexes, and modifying columns, can be atomically committed across multiple shards after the operations are pushed down to data nodes. | |
Fixed issue | The following issue is fixed: An error is occasionally reported if a window function includes count. |
The following issue is fixed: Incorrect results may be occasionally returned when you query the timestamp field in an archived table. | |
The following issue is fixed: The calculation result of a row expression is incorrect if the row expression is not pushed down for execution. | |
Release notes | |