From 85487d9a742ea217e828392b750c9fabeede8bc3 Mon Sep 17 00:00:00 2001 From: Aolin Date: Fri, 2 Dec 2022 11:38:00 +0800 Subject: [PATCH] AUTO_INCREMENT: MySQL compatibility mode GA (#11249) --- auto-increment.md | 6 +----- experimental-features.md | 1 - 2 files changed, 1 insertion(+), 6 deletions(-) diff --git a/auto-increment.md b/auto-increment.md index 1df2d5c7b8802..5cce561b0c31a 100644 --- a/auto-increment.md +++ b/auto-increment.md @@ -32,7 +32,7 @@ For performance reasons, `AUTO_INCREMENT` numbers are allocated in a batch of va > **Note:** > -> If you want the `AUTO_INCREMENT` numbers to be monotonic on all TiDB servers and your TiDB version is v6.4.0 or later, you can enable the [MySQL compatibility mode](#mysql-compatibility-mode) which is an experimental feature introduced in v6.4.0. +> If you want the `AUTO_INCREMENT` numbers to be monotonic on all TiDB servers and your TiDB version is v6.5.0 or later, it is recommended to enable the [MySQL compatibility mode](#mysql-compatibility-mode). The following is a basic example of `AUTO_INCREMENT`: @@ -355,10 +355,6 @@ The value (ID) implicitly assigned to auto-increment columns satisfies the follo TiDB v6.4.0 introduces a centralized auto-increment ID allocating service. In each request, an auto-increment ID is allocated from this service instead of caching data in TiDB instances. -> **Warning:** -> -> This is still an experimental feature. It is **NOT** recommended that you use it in the production environment. - Currently, the centralized allocating service is in the TiDB process and works like DDL Owner. One TiDB instance allocates IDs as the primary node and other TiDB instances work as secondary nodes. To ensure high availability, when the primary instance fails, TiDB starts automatic failover. To use the MySQL compatibility mode, you can set `AUTO_ID_CACHE` to `1` when creating a table: diff --git a/experimental-features.md b/experimental-features.md index eec6b510cade9..262e0b87f90ea 100644 --- a/experimental-features.md +++ b/experimental-features.md @@ -37,7 +37,6 @@ Elastic scheduling feature. It enables the TiDB cluster to dynamically scale out + [Range INTERVAL partitioning](/partitioned-table.md#range-interval-partitioning) (Introduced in v6.3.0) + [Add index acceleration](/system-variables.md#tidb_ddl_enable_fast_reorg-new-in-v630) (Introduced in v6.3.0) + [Restore a cluster to a specific point in time using the `FLASHBACK CLUSTER TO TIMESTAMP` syntax](/sql-statements/sql-statement-flashback-to-timestamp.md) (Introduced in v6.4.0) -+ [`AUTO_INCREMENT` MySQL compatibility mode](/auto-increment.md#mysql-compatibility-mode) (Introduced in v6.4.0) ## Storage