This topic describes the release notes for AnalyticDB for MySQL in 2020 and earlier and provides links to the relevant references.
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.
July 2020
V3.1.1.6
Category | Feature | Description | References |
New feature | Timestamp and Datetime columns | When the MODIFY COLUMN statement is executed to modify a Timestamp or Datetime column, the ON UPDATE CURRENT_TIMESTAMP clause is supported. | None |
Table and column naming conventions | Table and column names support Chinese characters. | None | |
Requirements for creating an OSS external table | The following requirements must be met when you create an OSS external table:
| Use external tables to import data to Data Warehouse Edition | |
| The | ||
Optimized feature | Fields of the BOOLEAN type | The default values for the fields of the BOOLEAN type can be 0 or 1. | None |
SHOW DATABASES | The permissions to list databases can be granted when the SHOW DATABASES statement is executed. | None |
April 2020
V3.0.9.6
The following database software upgrades are performed for users of AnalyticDB for MySQL Basic Edition to improve service quality.
Category | Feature | Description | References |
New feature | Geometry functions | Geometry functions are supported. | |
JSON_EXTRACT() function | The JSON_EXTRACT() function is supported. | ||
INSERT INTO VALUES(FROM_UNIXTIME(...)) | The | None | |
Nested-loop join (NLJ) | NLJ is supported for data join. | None | |
Power BI connection | Power BI can be connected to the protocol layer. | None | |
Database naming conventions | Hyphens (-) can be included in database names. Note Hyphens (-) must be enclosed in grave accents (``). | None | |
Optimized feature | Zero dates | Zero dates (0000-00-00) are converted to NULL. | None |
DIV() function of the DECIMAL type | The DIV() function of the DECIMAL type is supported as in MySQL. | ||
CAST() function of the JSON type | The CAST() function is supported for JSON data as in MySQL and Apache Hive. | ||
Slow query logging threshold | The slow query logging threshold is set to 1 second. | None |
March 2020
V3.0.9
Category | Feature | Description | References |
New feature | JSON data types and related JSON functions | Complex JSON data types and related JSON functions are supported. | |
|
| None | |
Optimized feature | Maximum number of tables | The maximum number of tables that can be created in a Cluster Edition cluster of the minimum specifications is increased from 512 to 800. The minimum specifications indicate that the Cluster Edition cluster has only two node groups. | None |
Compatibility with DDL statements | Compatibility with DDL statements in AnalyticDB for MySQL V2.0 is improved to enable smooth data migration to AnalyticDB for MySQL V3.0 clusters. Your business is not affected during data migration. | None | |
Compatibility with business intelligence (BI) tools | AnalyticDB for MySQL V3.0 improves compatibility with BI tools and is fully compatible with Power BI. |
February 2020
V3.0.8
Category | Feature | Description | References |
New feature | MariaDB JDBC Connector | MariaDB Java Database Connectivity (JDBC) Connector is supported. | None |
Specifications applicable to Cluster Edition | The storage-intensive specification S8 is added for AnalyticDB for MySQL Cluster Edition clusters. S8 is ideal for scenarios that do not require high concurrency and performance. | None | |
Flexible purchase of clusters | Node groups can be purchased and scaled out in pairs. This allows you to purchase clusters on demand and reduces costs. | None | |
Availability in Alibaba Finance Cloud | AnalyticDB for MySQL is available in the China East 1 Finance, China East 2 Finance, and China South 1 Finance regions of Alibaba Finance Cloud. | None | |
Availability on the international site (alibabacloud.com) | AnalyticDB for MySQL is available in the China (Hong Kong), Indonesia (Jakarta), and Malaysia (Kuala Lumpur) regions. | None | |
Optimized feature | Time types | The TIMESTAMP and DATETIME data types are compatible with the NO_ZERO_DATE mode of MySQL SQL_MODE. | None |
December 2019
V3.0.7
Category | Feature | Description | References |
New feature | Specification C24 | The compute-intensive specification C24 is added for AnalyticDB for MySQL clusters. C24 is ideal for scenarios that require sophisticated computing capabilities. | None |
Configuration upgrade | Cluster specifications can be upgraded. You can perform switchovers between two of the following specifications within seconds: C8, C4, and C24. | None | |
Monitoring and alerting | The monitoring and alerting feature is supported. You can use CloudMonitor to set thresholds for all metrics. An alert is triggered when a threshold is reached. | ||
Query termination | The query termination feature is supported. You can view and terminate running queries in real time in the AnalyticDB for MySQL console. | None | |
Data synchronization from PolarDB-X to AnalyticDB for MySQL | Data Transmission Service (DTS) can be used to synchronize data from PolarDB-X to AnalyticDB for MySQL in real time for data analytics. | None | |
Availability on the international site (alibabacloud.com) | AnalyticDB for MySQL is released for international use. This service is available in the Singapore and Japan (Tokyo) regions. | None | |
Optimized feature | View creation | Window functions can be used to create views. | None |
Use scenarios of CTEs | CTEs can be used in the INSERT SELECT FROM clause. |
September 2019
V3.0.6
Category | Feature | Description | References |
New feature | Specification C4 | The specification C4 is added to simplify the use of AnalyticDB for MySQL. We recommend that you use this specification in learning. | None |
COLLECT_SET() function | The COLLECT_SET() function is supported. | None | |
Optimized feature | Creation and scaling time for clusters | The amount of time spent on creating and scaling clusters is shortened to reduce costs. | None |
August 2019
V3.0.5
Category | Feature | Description | References |
New feature | Default column value | The default value of a column can be set to the current time. Example: | None |
Oracle GoldenGate (OGG) | OGG is supported in AnalyticDB for MySQL to enhance data synchronization from Oracle to AnalyticDB for MySQL. | None | |
Disk resizing | Flexible disk resizing is supported. This allows you to resize disks on demand and reduces costs. | None | |
Availability in Alibaba Finance Cloud | AnalyticDB for MySQL is available in Alibaba Finance Cloud. | None | |
Virtual e-commerce logistics platforms and CloudTmall | AnalyticDB for MySQL is available in virtual e-commerce logistics platforms and CloudTmall. | None | |
Optimized feature | Error message returned for modifying non-auto-increment keys | The error message that is returned when you change non-auto-increment keys to auto-increment keys is optimized to facilitate your understanding. | None |
July 2019
V3.0.4
Category | Feature | Description | References |
New feature | Backup and restoration | The backup and restoration feature is supported. You can restore data from backup sets to a point in time to maximize data restorability. | None |
LOAD DATA | The LOAD DATA LOCAL INFILE statement is supported. | ||
Flexible purchase of services | Node groups can be purchased in pairs. For example, you can set Node Groups to 2, 4, 6, or 8 on the AnalyticDB for MySQL buy page. | None | |
Data types and important functions | New data types and specific important functions are supported. | None | |
Optimized feature | Compatibility | AnalyticDB for MySQL is fully compatible with Navicat, FineReport, and FineBI, and its compatibility with Sequel Pro is greatly improved. | None |