This topic describes the release notes for AnalyticDB for MySQL and provides links to the relevant references.
March 2022
Category | Feature | Description | References |
---|---|---|---|
New feature | Schema optimization | The schema optimization feature is supported to provide optimization suggestions of the hot and cold data optimization, index optimization, and distribution key optimization types based on intelligent statistic analysis. This feature can help reduce costs and improve efficiency for the use of AnalyticDB for MySQL clusters. | Schema optimization |
December 2021
V3.1.4.13 to V3.1.4.16
Category | Feature | References | |
---|---|---|---|
New feature | Two data replicas and one log replica are configured based on the Raft algorithm to ensure data reliability and reduce storage overheads. | None | |
The high availability feature of the nameservice of Apsara File Storage for HDFS is supported when data is exported to HDFS. | Use external tables to export data from AnalyticDB for MySQL to Apsara File Storage for HDFS | ||
Optimized feature |
|
None | |
Fixed issue |
|
None |
September 2021
V3.1.4.12
Category | Feature | References | |
---|---|---|---|
Optimized feature | The performance of the hash join algorithm to create a hash table is improved. | None | |
Fixed issue |
|
None |
August 2021
V3.1.4.11
Category | Feature | Description | References |
---|---|---|---|
New feature | API operations related to cluster running reports | API operations can be called to query metrics in a cluster running report. The following
API operations are available:
|
|
Optimized feature |
|
None | |
Fixed issue |
|
None |
V3.1.4.10
Category | Feature | Description | References |
---|---|---|---|
New feature | O&M event management | The database upgrade time can be viewed and adjusted in the AnalyticDB for MySQL console. | Manage O&M events |
Optimized feature |
|
None | |
Fixed issue |
|
None |
July 2021
V3.1.4.9
Category | Feature | Description | References |
---|---|---|---|
New feature | Data import to and export from Apsara File Storage for HDFS by using external tables | External tables can be used to import Apsara File Storage for HDFS data to AnalyticDB MySQL and export AnalyticDB MySQL data to Apsara File Storage for HDFS. | Use external tables to import data from Apsara File Storage for HDFS to AnalyticDB
for MySQL Use external tables to export data from AnalyticDB for MySQL to Apsara File Storage for HDFS |
SQL diagnostics | The details of SQL queries can be viewed and filtered based on categories such as the top 100 most time-consuming queries and queries that failed to be executed. Also, SQL queries can be optimized based on diagnostic results and optimization suggestions. | Introduction to SQL diagnostics | |
End-to-end data management | An end-to-end data management portal is added to the AnalyticDB for MySQL console. Data assets can be managed and jobs can be developed and scheduled by using Data Management (DMS). | Manage data assets | |
Custom analyzers and dictionaries in full-text search scenarios | Custom analyzers and dictionaries can be configured in full-text search scenarios. | Custom analyzers and dictionaries | |
Optimized feature |
|
None | |
Fixed issue |
|
None |
March 2021
V3.1.1.9 to V3.1.3.9
Category | Feature | Description | References |
---|---|---|---|
New feature | Computing resource grouping | The resource pool feature is provided to isolate computing resources by group in clusters in elastic mode. | Manage resource pools |
Tiered storage of hot and cold data | Table data of clusters in elastic mode can be defined as hot or cold data. You can switch between hot and cold storage. | Separation of hot and cold data storage | |
Cluster mode change | Clusters can be changed from the reserved mode to the elastic mode. | None | |
Compatibility with time formats in AnalyticDB for MySQL V2.0 | Time formats in AnalyticDB for MySQL V2.0 are supported. Example: 2020-08-03T23:59:59 .
|
None | |
Index creation or deletion for JSON fields by executing the ALTER TABLE statement | Indexes for JSON fields can be disabled by executing the ALTER TABLE statement. | ALTER TABLE | |
BINARY type | The BINARY type is supported for the metadata of the protocol layer. | None | |
Export of file headers during export from AnalyticDB for MySQL to a single Object Storage Service (OSS) object | File headers can be exported when you export data from AnalyticDB for MySQL to a single OSS object by using an external table. | Use external tables to export data from AnalyticDB for MySQL to OSS | |
Maximum number of rows that can be generated in an object when you export data from AnalyticDB for MySQL to OSS by using an external table | If the number of exported rows exceeds the maximum number, extra rows are exported to one or more new objects. You can specify both the maximum size and maximum number of rows in an object. Written data that first triggers the limit is exported to a new object. | None | |
SQL plan module | Execution plans of slow SQL queries can be viewed in the AnalyticDB for MySQL console. | Query process and execution plan | |
INSERT INTO SELECT ON DUPLICATE KEY UPDATE
|
This query is supported when the input values in the UPDATE column are constants or when the input values in the UPDATE column are those in the SELECT column. | None | |
File format of OSS external tables | The ORC format is supported for OSS external tables. | None | |
Priority of the BATCH LOAD statement | Hints can be used to specify the priority of the BATCH LOAD statement. | None | |
Optimized feature | Performance of the LIMIT n statement | Performance is improved when you use the pushdown logic of the LIMIT n statement to filter data. | None |
Compatibility | The table creation statement is compatible with the BOOLEAN type. | None | |
Database naming conventions | Database names can start with an uppercase letter or an underscore (_). | None | |
Fixed issue | The issue that may cause index exceptions when multiple indexes are created or deleted is fixed. | ||
The issue that may cause java.lang.NullPointerException errors is fixed. Such errors may be returned when you execute the INSERT statement
in scenarios where a table does not exist .
|
|||
The issue that may cause data query exceptions is fixed. Such exceptions may occur when OSS partitioned tables are pushed down if Parquet-formatted files contain partition fields. | |||
The issue that may cause the Premature end of Content-Length error to occasionally occur when you access OSS is fixed. | |||
The issue that may cause com.alibaba.fastsql.sql.ast.expr.SQLMethodInvokeExpr cannot be cast to com.alibaba.fastsql.sql.ast.SQLName errors when you execute the ADD KEY statement is fixed.
|
|||
The issue that may cause no composite key to add errors due to composite keys when tables are managed in hot or cold storage is fixed.
|
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 from OSS to AnalyticDB for MySQL | |
CREATE TABLE AS SELECT |
The CREATE TABLE AS SELECT statement can be executed to create a table.
|
CTAS | |
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 | |
Fixed issue | The issue that may cause Not a Number (NaN) errors in statistics is fixed. | ||
The issue that may cause the name of a table created by executing CREATE TABLE to be the same as an existing view name is fixed. | |||
The issue that may cause queries to be more slowly processed when a number of queries fail is fixed. | |||
The issue that may cause only part of data to be returned is fixed. This error may occur when a statement that contains GROUP BY is executed to query data from a table that has a multi-value column. | |||
The issue that may cause only part of data to be read from the end of a table is fixed. This error may occur after the data in an OSS external table is compressed by using GZIP. |
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. | Operation functions |
JSON_EXTRACT function | The JSON_EXTRACT function is supported. | JSON _EXTRACT | |
INSERT INTO VALUES(FROM_UNIXTIME(...)) | The INSERT INTO VALUES(FROM_UNIXTIME(...)) statement is supported.
|
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 backticks (``).
|
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. | DIV | |
CAST function of the JSON type | The CAST function is supported for JSON data as in MySQL and Apache Hive. | JSON | |
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. | |
SELECT NOW() |
The SELECT NOW() statement is 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. | Power BI | |
Fixed issue | The issue that may cause unclear errors when the used disk capacity exceeds the threshold during data loading is fixed. |
February 2020
V3.0.8
Category | Feature | Description | References |
---|---|---|---|
New feature | MariaDB JDBC Connector | MariaDB Connector/J 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), Malaysia (Kuala Lumpur), India (Mumbai), and Australia (Sydney) 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 |
Fixed issue | The issue that may cause incompatibility in boundary processing of the SUBSTRING_INDEX function is fixed. |
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. | Set an alert rule | |
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 | |
Synchronization from PolarDB-X 1.0 to AnalyticDB for MySQL | Data Transmission Service (DTS) can be used to synchronize data from PolarDB-X 1.0 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 (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. | INSERT SELECT FROM |
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 scale-out time for clusters | The amount of time spent on creating and scaling out clusters is shortened to reduce costs. | None |
Fixed issue | The issue that may cause ineffective IF NOT EXIST for external tables is fixed. |
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: gmt_create datetime NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP .
|
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 | The incremental backup and restoration features are 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. | LOAD DATA LOCAL INFILE | |
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 some 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 |
Fixed issue | The issue that may cause failed support for multiple columns during subquery comparison is fixed. |