LibraDB Engine Core Version Release Notes

Last updated: 2024-12-11 14:51:53

This document introduces the LibraDB engine kernel version updates of TDSQL-C for MySQL. For detailed product features, see LibraDB Engine Features.
Version Number Rule
The kernel version of the LibraDB engine can be found in the instance details. The version number is composed of 4 numbers, separated by dots. Different numbers represent different version meanings, as detailed below.
First number: represents the major version of a product. When the current version of the product is not compatible with the previous version, this number is increased by 1.
Second number: represents the iteration version of a product. When important features are added to the product, this iteration number is defined based on the current year and month.
Third number: represents the minor version of a product. When feature optimizations or bug fixes are made to the product, this number is increased by 1.
Fourth number: represents the patch version of a product. When an urgent bug is found and needs to be fixed, a patch upgrade will be performed for the version.
Version Updates
Minor Version
Description
1.2404.15.2
This version is a bug fix release, mainly fixing defects in versions earlier than 1.2404.15.1.
Bug fixes
Fixed an occasional instance crash issue that occurred when data queries were executed during high-concurrency updates on read-write instances after loading as a column-based table.
1.2404.15.1
System optimizations
Optimized the default value of the database log retention size. Adjustments are as follows: When the instance disk specification is less than or equal to 500 GB, a maximum of 5 GB logs are retained by default; when the instance disk specification is greater than 500 GB, a maximum of 10 GB logs are retained by default.
The late materialization feature of the read-only analysis engine is enabled by default. For detailed information on late materialization tuning capabilities, refer to Late Materialization.
Supported loading tables starting with "_" into the read-only analysis engine.
Optimized the efficiency of restarting the read-only analysis engine.
Bug fixes
Fixed an issue where certain versions of Navicat encountered insufficient permissions errors when connecting to the read-only analysis engine.
Fixed the data loading error in the read-only analysis engine when DDL statements are executed consecutively.
Fixed the syntax compatibility issue with default (0) in the create table statement.
1.2404.10.0
Feature updates
Supported the date_sub function.
Supported manual execution of table statistical information collection. For details, see Statistical Information Collection.
Supported synchronous loading of enum data in special scenarios.
 Note:
Although the loading of enum data into the read-only analysis engine in special scenarios is supported, queries of enum data are still not supported.
System optimizations
Modified the kernel to reduce the number of versions of expired data retained in storage, avoiding excessive disk space occupancy caused by retaining too many data snapshots.
Optimized the proportion of resources occupied by the kernel during data cleanup, preventing excessive system resource occupancy from impacting users' SQL execution performance.
Modified the log level of kernel information to avoid excessive disk space occupancy due to too much log printing.
Adjusted the maximum value of the "Storage" field from the previous default value 1 MB to 5 MB.
Optimized the error message for querying data before it is fully loaded into the read-only analysis engine. Now, it clearly indicates that queries can only be performed after full data is loaded.
Optimized the error messages for unsupported data types or functions during execution. Now, unsupported items are clearly indicated in the error messages.
Optimized the trigger frequency and selection logic for background tasks within the system to avoid the impact of background task triggers on users' SQL execution performance.
Optimized the version number information displayed when the read-only analysis engine instance was accessed through a MySQL client to avoid confusion.
1.2404.7
Feature updates
Supported real-time loading of ultra-large-scale data into the read-only analysis engine.
Supported ultra-high performance complex data queries.
Note:
This version is the first newly launched LibraDB engine kernel version of TDSQL-C for MySQL.

tencent cloud

Recent Pages

LibraDB Engine Core Version Release Notes

Version Number Rule

Version Updates

Was this page helpful?

Was this page helpful?

Minor Version	Description
1.2404.15.2	This version is a bug fix release, mainly fixing defects in versions earlier than 1.2404.15.1. Bug fixes Fixed an occasional instance crash issue that occurred when data queries were executed during high-concurrency updates on read-write instances after loading as a column-based table.
1.2404.15.1	System optimizations Optimized the default value of the database log retention size. Adjustments are as follows: When the instance disk specification is less than or equal to 500 GB, a maximum of 5 GB logs are retained by default; when the instance disk specification is greater than 500 GB, a maximum of 10 GB logs are retained by default. The late materialization feature of the read-only analysis engine is enabled by default. For detailed information on late materialization tuning capabilities, refer to Late Materialization. Supported loading tables starting with "_" into the read-only analysis engine. Optimized the efficiency of restarting the read-only analysis engine. Bug fixes Fixed an issue where certain versions of Navicat encountered insufficient permissions errors when connecting to the read-only analysis engine. Fixed the data loading error in the read-only analysis engine when DDL statements are executed consecutively. Fixed the syntax compatibility issue with default (0) in the create table statement.
1.2404.10.0	Feature updates Supported the date_sub function. Supported manual execution of table statistical information collection. For details, see Statistical Information Collection. Supported synchronous loading of enum data in special scenarios. Note: Although the loading of enum data into the read-only analysis engine in special scenarios is supported, queries of enum data are still not supported. System optimizations Modified the kernel to reduce the number of versions of expired data retained in storage, avoiding excessive disk space occupancy caused by retaining too many data snapshots. Optimized the proportion of resources occupied by the kernel during data cleanup, preventing excessive system resource occupancy from impacting users' SQL execution performance. Modified the log level of kernel information to avoid excessive disk space occupancy due to too much log printing. Adjusted the maximum value of the "Storage" field from the previous default value 1 MB to 5 MB. Optimized the error message for querying data before it is fully loaded into the read-only analysis engine. Now, it clearly indicates that queries can only be performed after full data is loaded. Optimized the error messages for unsupported data types or functions during execution. Now, unsupported items are clearly indicated in the error messages. Optimized the trigger frequency and selection logic for background tasks within the system to avoid the impact of background task triggers on users' SQL execution performance. Optimized the version number information displayed when the read-only analysis engine instance was accessed through a MySQL client to avoid confusion.
1.2404.7	Feature updates Supported real-time loading of ultra-large-scale data into the read-only analysis engine. Supported ultra-high performance complex data queries. Note: This version is the first newly launched LibraDB engine kernel version of TDSQL-C for MySQL.

tencent cloud

Sign Up

Log in

Recent Pages

LibraDB Engine Core Version Release Notes

Version Number Rule

Version Updates

Was this page helpful?

Was this page helpful?