LibraDB Engine Core Version Release Notes

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 viewed in instance details. The version number is composed of four digits, separated by dots. Different digits represent different version meanings. The details are as follows.
First digit: represents the main version of the product. When the current version of the product is not compatible with the previous version, this version number will be increased by 1.
Second digit: represents the iterative version of the product. When important features are added to the product, this iterative number will be defined based on the current year and month.
Third digit: represents the minor version of the product. When some optimization features or bug fixes are made to the product, this version number will be increased by 1.
Fourth digit: represents the patch version of the product. When it is found that there is a bug urgently to be fixed in the product, a patch upgrade will be performed on this version.
Version Update Description
Minor Version
Description
1.2404.19.1
This version is a problem fix version, which mainly fixes the defects in versions before 1.2404.19.0.
Bug fixes
Fixed an inconsistency issue with view definers when loading views into a read-only analytics engine.
Fixed the problem of user synchronization failure of the mysql.user system table when encountering a user with an empty password.
Fixed an execution error issue caused by executing DDL during SQL execution.
Fixed a write exception issue in the "Accelerated ETL Writeback" function when encountering constant columns.
1.2404.19.0
Feature updates
The current version supports access to the "Read-Only Analysis Engine" through the database proxy and using Hint syntax.
The ability to access the "Read-Only Analysis Engine" via the DMC is supported.
System optimizations
Optimized the memory management method of Sort operator and Aggregation operator to improve memory usage efficiency. After optimization, the memory can be released in advance when the Sort operator and Aggregation operator end execution, without waiting for the end of query execution.
Optimized the memory usage of Join result output, reducing the memory usage when the Join operator output result set is relatively large.
Optimized the allocation strategy of delayed materialization in primary key scenarios.
Bug fixes
Fixed the issue where Prepare Statement uses Plan Cache by default, resulting in multiple similar queries. When the constant parameter types are inconsistent, the previous cache plan is hit, resulting in query errors.
Fixed the query error issue in some scenarios when the output column in the Union All scenario involves VARCHAR type.
Fixed an issue where some metadata acquisition errors occurred due to insufficient permissions when DMC connected to the column storage engine.
Fixed a possible memory leak issue in scenarios where connections are frequently created.
Fixed the problem that temporary tables cannot be queried in the read-only analysis engine in PT change scenarios.
Fixed an issue where delayed materialization operators were not displayed in execution plans in certain scenarios.
Fixed an issue where the "Read-Only Analysis Engine" was unable to delete fields in a federated index.
Fixed the out-of-bounds issue of Runtime Filter allocation in multi-table Join scenarios.
Fixed the issue where Runtime filter filter data occasionally appears empty.
Fixed the error reporting issue when the NULLABLE type is inconsistent with the non-NULLABLE type in the Union All scenario.
1.2404.17.0
Feature updates
Supported FROM_UNIXTIME and UNIX_TIMESTAMP functions.
System optimizations
Optimized the system table query permission prompt when database client tools such as DBearer access the read-only analysis engine.
Optimized the error message when some unsupported functions report errors.
Bug fixes
Fixed the issue where the read-only analysis engine loads the timestamp field value in scenarios where the explicit_defaults_for_timestamp parameter values ​​of the read-write instance are different.
1.2404.16.0
Feature updates
Supports the use of "read-only analysis engine" to accelerate the execution of query statements in INSERT...SELECT..., and supports faster writing to read-write instances.
Supports query and synchronization of bit, enum, and set type data.
System optimizations
Optimized the naming format of some system tables to make them easier to understand, such as the SLOW_LOG table.
The current version adjusts the value size supported by ordinary columns to 16MB, compared with 5MB in the previous version
Optimized the logic of the StorageTableReader operator to obtain column names when the query plan is empty.
Bug fixes
Fixed the problem that in the subquery scenario, when the main query result is empty, the Apply operator logic is still used, causing the query to report an error.
Fixed the issue where the Apply operator caused a crash when competing with multiple threads.
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. Adjusted it as follows: When the instance disk specification is less than or equal to 500 GB, the default maximum log retention size is 5 GB; when the instance disk specification is greater than 500 GB, the default maximum log retention size is 10 GB.
The read-only analysis engine feature "Lazy Materialization" is enabled by default. For detailed information on lazy materialization tuning capabilities, see Lazy Materialization.
Supports the loading of tables starting with the "_" symbol into the read-only analysis engine.
Optimized the efficiency of restarting the read-only analysis engine.
 Issue Fixes
Resolved the issue that an error occurs due to insufficient permissions when some versions of Navicate are connected to the read-only analysis engine.
Fixed the issue that a data loading error occurs in the read-only analysis engine when DDL statements are executed continuously.
Resolved the syntax compatibility issue with default (0) in create table statements.
1.2404.10.0
 Feature Updates
Supports the date_sub function.
Supports users to manually perform statistical information collection for tables. For details, refer to Statistical Information Collection.
Supports the sync loading of enum data in special scenarios.
 Note:
Although loading enum into the read-only analysis engine in special scenarios is supported, querying data of the enum field type is still not supported.
System Optimizations
Modified the kernel to reduce the number of retained versions of expired data in storage, avoiding excessive disk space occupancy due to too many retained data snapshots.
Optimized the proportion of resources occupied by the kernel during data cleanup, preventing excessive system resource occupancy from impacting the user's SQL execution performance.
Modified the level of kernel information log printing to avoid excessive disk space occupancy due to excessive log printing.
Adjusted the maximum value of the single field "Storage" from the previously supported default of 1 MB to 5 MB.
Optimized error messages for data queries before data is fully loaded into the read-only analysis engine. Now, there is a clearer reminder that queries can be performed only after the full data is loaded.
Optimized error messages for some unsupported data types or functions during execution. Now, unsupported items can be clearly viewed from error messages.
Optimized the triggering frequency and selection logic for background tasks within the system to prevent the impact on the user's online SQL execution performance due to background task triggering.
Optimized the version number information displayed when a read-only analysis engine instance is 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.

Was this page helpful?

You can also Contact Sales or Submit a Ticket for help.

Yes

Minor Version	Description
1.2404.19.1	This version is a problem fix version, which mainly fixes the defects in versions before 1.2404.19.0. Bug fixes Fixed an inconsistency issue with view definers when loading views into a read-only analytics engine. Fixed the problem of user synchronization failure of the mysql.user system table when encountering a user with an empty password. Fixed an execution error issue caused by executing DDL during SQL execution. Fixed a write exception issue in the "Accelerated ETL Writeback" function when encountering constant columns.
1.2404.19.0	Feature updates The current version supports access to the "Read-Only Analysis Engine" through the database proxy and using Hint syntax. The ability to access the "Read-Only Analysis Engine" via the DMC is supported. System optimizations Optimized the memory management method of Sort operator and Aggregation operator to improve memory usage efficiency. After optimization, the memory can be released in advance when the Sort operator and Aggregation operator end execution, without waiting for the end of query execution. Optimized the memory usage of Join result output, reducing the memory usage when the Join operator output result set is relatively large. Optimized the allocation strategy of delayed materialization in primary key scenarios. Bug fixes Fixed the issue where Prepare Statement uses Plan Cache by default, resulting in multiple similar queries. When the constant parameter types are inconsistent, the previous cache plan is hit, resulting in query errors. Fixed the query error issue in some scenarios when the output column in the Union All scenario involves VARCHAR type. Fixed an issue where some metadata acquisition errors occurred due to insufficient permissions when DMC connected to the column storage engine. Fixed a possible memory leak issue in scenarios where connections are frequently created. Fixed the problem that temporary tables cannot be queried in the read-only analysis engine in PT change scenarios. Fixed an issue where delayed materialization operators were not displayed in execution plans in certain scenarios. Fixed an issue where the "Read-Only Analysis Engine" was unable to delete fields in a federated index. Fixed the out-of-bounds issue of Runtime Filter allocation in multi-table Join scenarios. Fixed the issue where Runtime filter filter data occasionally appears empty. Fixed the error reporting issue when the NULLABLE type is inconsistent with the non-NULLABLE type in the Union All scenario.
1.2404.17.0	Feature updates Supported FROM_UNIXTIME and UNIX_TIMESTAMP functions. System optimizations Optimized the system table query permission prompt when database client tools such as DBearer access the read-only analysis engine. Optimized the error message when some unsupported functions report errors. Bug fixes Fixed the issue where the read-only analysis engine loads the timestamp field value in scenarios where the explicit_defaults_for_timestamp parameter values of the read-write instance are different.
1.2404.16.0	Feature updates Supports the use of "read-only analysis engine" to accelerate the execution of query statements in INSERT...SELECT..., and supports faster writing to read-write instances. Supports query and synchronization of bit, enum, and set type data. System optimizations Optimized the naming format of some system tables to make them easier to understand, such as the SLOW_LOG table. The current version adjusts the value size supported by ordinary columns to 16MB, compared with 5MB in the previous version Optimized the logic of the StorageTableReader operator to obtain column names when the query plan is empty. Bug fixes Fixed the problem that in the subquery scenario, when the main query result is empty, the Apply operator logic is still used, causing the query to report an error. Fixed the issue where the Apply operator caused a crash when competing with multiple threads.
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. Adjusted it as follows: When the instance disk specification is less than or equal to 500 GB, the default maximum log retention size is 5 GB; when the instance disk specification is greater than 500 GB, the default maximum log retention size is 10 GB. The read-only analysis engine feature "Lazy Materialization" is enabled by default. For detailed information on lazy materialization tuning capabilities, see Lazy Materialization. Supports the loading of tables starting with the "_" symbol into the read-only analysis engine. Optimized the efficiency of restarting the read-only analysis engine. Issue Fixes Resolved the issue that an error occurs due to insufficient permissions when some versions of Navicate are connected to the read-only analysis engine. Fixed the issue that a data loading error occurs in the read-only analysis engine when DDL statements are executed continuously. Resolved the syntax compatibility issue with default (0) in create table statements.
1.2404.10.0	Feature Updates Supports the date_sub function. Supports users to manually perform statistical information collection for tables. For details, refer to Statistical Information Collection. Supports the sync loading of enum data in special scenarios. Note: Although loading enum into the read-only analysis engine in special scenarios is supported, querying data of the enum field type is still not supported. System Optimizations Modified the kernel to reduce the number of retained versions of expired data in storage, avoiding excessive disk space occupancy due to too many retained data snapshots. Optimized the proportion of resources occupied by the kernel during data cleanup, preventing excessive system resource occupancy from impacting the user's SQL execution performance. Modified the level of kernel information log printing to avoid excessive disk space occupancy due to excessive log printing. Adjusted the maximum value of the single field "Storage" from the previously supported default of 1 MB to 5 MB. Optimized error messages for data queries before data is fully loaded into the read-only analysis engine. Now, there is a clearer reminder that queries can be performed only after the full data is loaded. Optimized error messages for some unsupported data types or functions during execution. Now, unsupported items can be clearly viewed from error messages. Optimized the triggering frequency and selection logic for background tasks within the system to prevent the impact on the user's online SQL execution performance due to background task triggering. Optimized the version number information displayed when a read-only analysis engine instance is 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

New User Offers

Next-Generation CDN：EdgeOne

Elasticsearch Service free trial

Free Tier

Tencent Cloud Startup Program

Special Offers

Lighthouse Special Offers

Cloud Object Storage Special Offers

Featured Products

New Products

Education

Tencent Cloud Online Education Solutions

Gaming

Gaming Solution

Game Media Solutions

E-commerce

E-commerce retail solutions

Audio & Video

Audio/Video Solution

LVB Recording Solution

Interactive Classroom Solution

Interactive Live Streaming Solution

Audio Chat Social Networking Solution

Financial Services

Financial Services Solution

Compute

Cloud Virtual Machine

Auto Scaling

Batch Compute

CVM Dedicated Host

Database

TencentDB for MySQL

TencentDB for Redis®

TencentDB for CTSDB

TDSQL for MySQL

Data Transfer Service

TencentDB for MongoDB

TencentDB for PostgreSQL

TencentDB for SQL Server

Video Service

Cloud Streaming Services

Video on Demand

Media Processing Service

Cloud Application Rendering

Cloud Contact Center

Game Multimedia Engine

Chat

Real-time Communication

Tencent Effect SDK

AI and Machine Learning

Image Creation Large Model

Face Fusion

eKYC

Optical Character Recognition

Video Creation Large Model

Industry Applications

Tencent HealthCare Omics Platform

Container and Middleware

TDMQ for CKafka

Serverless Cloud Function

Tencent Kubernetes Engine

Tencent Kubernetes Engine for Serverless

Networking

Cloud Load Balancer

Virtual Private Cloud

Direct Connect

Cloud Connect Network

NAT Gateway

VPN Connection

Bandwidth Package

Anycast Internet Acceleration

Elastic Network Interface

Flow Logs

Global Application Acceleration Platform

Security

Captcha

Cloud Workload Protection Platform

Data Security Governance Center

Key Management Service