This topic describes the product feature updates for AnalyticDB for MySQL.
Usage notes
Take note of the following items during minor version updates of AnalyticDB for MySQL clusters:
-
For AnalyticDB for MySQL clusters in reserved mode for Cluster Edition or AnalyticDB for MySQL clusters in elastic mode for Cluster Edition that have 32 cores or more, data read and write operations are not interrupted when engine versions are updated. Within 5 minutes before the update is complete, queries may encounter transient connections.
-
For AnalyticDB for MySQL clusters in elastic mode for Cluster Edition that have 8 or 16 cores, data write operations may be interrupted for 30 minutes when engine versions are updated. Within 5 minutes before the update is complete, queries may encounter transient connections.
-
Minor version updates of AnalyticDB for MySQL clusters do not affect database access, account management, database management, or IP address whitelist settings.
-
During a minor version update of an AnalyticDB for MySQL cluster, network jitters may occur and affect write and query operations. Make sure that your application is configured to automatically reconnect to the AnalyticDB for MySQL cluster.
-
During a minor version update of an AnalyticDB for MySQL cluster, the cluster may encounter transient connections. Make sure that your application is configured to automatically reconnect to the AnalyticDB for MySQL cluster.
If you do not need to update the minor version of your AnalyticDB for MySQL cluster or an error occurs during the update process, you can cancel the scheduled minor version update. You can cancel only the scheduled events of a minor version update. For more information, see the "Cancel scheduled events" section of the Manage O&M events topic.
If the minor version of your AnalyticDB for MySQL cluster is earlier than the latest minor version, Alibaba Cloud pushes a notification at an irregular interval to inform you that the cluster needs to be updated to the latest minor version. We recommend that you update the minor version of your AnalyticDB for MySQL cluster at the earliest opportunity within six months after you receive the notification. Otherwise, you shall assume all liabilities for risks such as service interruptions and data loss.
February 2026
V3.2.6
Category | Name | Description | References |
New Feature | Materialized view observability | AnalyticDB for MySQL enhances observability across the entire lifecycle of materialized views. You can promptly detect latency events, pinpoint the root cause in complex topologies, and obtain clear insights for cost governance. | |
Import data from external cloud storage by using external tables | You can now import data from HDFS, AWS S3, Azure Blob Storage, or Google Cloud Storage by using an external table. | ||
Enhancement | Manage materialized views | You can now rename materialized views. | |
Asynchronous tasks | You can now specify a task alias when you submit an asynchronous task and use the alias to query the task status. |
V3.2.5
Category | Name | Description | References |
New Feature | MD5_MUR function | Converts a string to a numeric value. | |
Row store engine | The AnalyticDB for MySQL row store engine is a high-concurrency, real-time engine for row-oriented tables. It is designed for high-concurrency point query workloads based on primary keys and fast queries with multi-column projections. | ||
Materialized view AI recommendation | AnalyticDB for MySQL analyzes historical queries to automatically recommend and create materialized views, delivering transparent query acceleration with zero impact on business operations. | Automatically build materialized views based on query history | |
JSON_TABLE table function | Supports using the unnest function to expand JSON arrays. | ||
xuanwu_v2 table-level binlog | You can now enable binlog for xuanwu_v2 tables. | ||
Enhancement | Config and Hint parameters | Supports type validation for Config parameters. |