This topic describes the 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.
December 2025
Category | Feature | Description | References |
New | Change edition | You can now upgrade AnalyticDB for MySQL from Basic Edition to Enterprise Edition. | |
Managed lake storage authorization | You can now manage authorization for AnalyticDB for MySQL lake storage through a visual interface. | ||
Kafka data synchronization | You can use the AnalyticDB Pipeline Service (APS) to create Kafka synchronization tasks. These tasks synchronize data in real time from a specified offset in Kafka to your data warehouse. |
August 2025
V3.2.4
Category | Feature | Description | References |
New | Table-level partition lifecycle management (LIFECYCLE) | You can now use ALTER TABLE to disable partition lifecycle rules and automatic data cleanup for a table. | |
Paimon external tables | You can now create Paimon external tables. | ||
MaxCompute external tables | You can now create MaxCompute external tables by using an external server. | ||
Drop partitions | You can now use ALTER TABLE to drop partitions from a table. When a partition is dropped, its data is permanently removed and cannot be recovered. | ||
MAX_PT function | You can use the MAX_PT function to query the maximum value of the level-1 partition in a MaxCompute partitioned external table. This avoids scanning all partitions, which significantly improves query processing speed and computing efficiency. | ||
Enhancement | Display underlying error messages when creating external tables | When you create a MySQL external table, underlying error messages are now displayed to help you locate and troubleshoot issues. | None |
June 2025
Category | Feature | Description | References |
New | Change a single-zone deployment to a multi-zone deployment | You can now change a single-zone cluster to a multi-zone cluster. | |
Cross-region backup | The cross-region backup feature provides region-level disaster recovery for AnalyticDB for MySQL. After you enable this feature, full backups of your cluster are automatically copied to a target region as cross-region backup sets. You can use these cross-region backup sets to restore a new cluster. |
May 2025
Category | Feature | Description | References |
New | Managed lake storage | Managed lake storage is now available for Enterprise Edition, Basic Edition, and Data Lakehouse Edition clusters in the Indonesia (Jakarta) region. This includes support for features such as Lake Cache. | |
Managed Ray Service | Managed Ray Service (AnalyticDB Ray) is built on open-source Ray and enhanced for the AnalyticDB for MySQL lakehouse platform. It features an optimized kernel, simplified cluster O&M, and deep integration to help you build a unified Data+AI architecture. | ||
URL parsing functions | The service now supports URL parsing functions, including URL_DECODE, URL_ENCODE, and PARSE_URL. | ||
BI tools | Power BI now supports accessing data in AnalyticDB for MySQL in DirectQuery mode by using a custom connector. |
April 2025
Category | Feature | Description | References |
New | New region available for the Lake Cache feature | The Lake Cache feature is now available for Enterprise Edition, Basic Edition, and Data Lakehouse Edition clusters in the Indonesia (Jakarta) region. | |
Change cloud disk level | You can now change the cloud disk level for Enterprise Edition, Basic Edition, and Data Lakehouse Edition clusters. |
March 2025
Category | Feature | Description | References |
New | Multi-zone deployment | You can create Enterprise Edition clusters that use a multi-zone deployment. Compared with single-zone clusters, multi-zone clusters provide higher disaster recovery capabilities and can withstand zone-level failures. In the event of a failure, services are automatically switched to a secondary zone to ensure business continuity. | |
Storage plans |
| ||
SSL encryption | You can use SSL encryption to encrypt data transmitted between clients and your Enterprise Edition, Basic Edition, or Data Lakehouse Edition clusters. This prevents data from being intercepted, monitored, or tampered with by third parties. | ||
Column addition or removal for external tables | You can now add columns to or remove columns from external tables in Enterprise Edition, Basic Edition, and Data Lakehouse Edition clusters. |
V3.2.3
Category | Feature | Description | References |
New | Fast refresh of materialized views |
| |
Table recycle bin | After you enable the table recycle bin feature, deleted tables are temporarily moved to the recycle bin. This allows you to restore accidentally deleted data. | ||
Change the number of shards | The number of shards affects the upper and lower limits for horizontal scaling. You can change the number of shards for Data Warehouse Edition clusters in the console. | ||
Iceberg external tables | You can now create Iceberg external tables. |
February 2025
Category | Feature | Description | References |
New | Enterprise Edition and Basic Edition released | AnalyticDB for MySQL Enterprise Edition and Basic Edition are released.
| |
Zero-ETL | Zero-ETL supports MongoDB as a data source. You can create a MongoDB synchronization task for end-to-end data synchronization that integrates transaction processing and data analytics.MongoDB | ||
Modify columns of external tables | You can now modify the properties of columns, such as column names and data types, for external tables in Enterprise Edition, Basic Edition, and Data Lakehouse Edition clusters. |
January 2025
Category | Feature | Description | References |
Enhancement | Cold data storage upgraded from locally redundant storage (LRS) to zone-redundant storage (ZRS) | After the upgrade to zone-redundant storage (ZRS), cold data is redundantly stored across multiple zones in the same region. This ensures data access even if a zone becomes unavailable. |