From 5ad5af7a748b2cc6907ef60839cbb532d161990c Mon Sep 17 00:00:00 2001 From: Aolin Date: Thu, 12 Sep 2024 11:11:57 +0800 Subject: [PATCH] fix: remove Chinese doc links (#18886) --- develop/dev-guide-create-table.md | 2 +- develop/dev-guide-insert-data.md | 2 +- develop/dev-guide-playground-gitpod.md | 2 +- dm/task-configuration-file-full.md | 2 +- migrate-large-mysql-shards-to-tidb.md | 2 +- placement-rules-in-sql.md | 2 +- tidb-resource-control.md | 4 ++-- 7 files changed, 8 insertions(+), 8 deletions(-) diff --git a/develop/dev-guide-create-table.md b/develop/dev-guide-create-table.md index ff62537806517..6994ab76e6dc6 100644 --- a/develop/dev-guide-create-table.md +++ b/develop/dev-guide-create-table.md @@ -106,7 +106,7 @@ A [primary key](/constraints.md#primary-key) is a column or a set of columns in > > - In **InnoDB**: A **primary key** is unique, not null, and **index clustered**. > -> - In TiDB: A **primary key** is unique and is not null. But the primary key is not guaranteed to be a **clustered index**. Instead, another set of keywords `CLUSTERED` / `NONCLUSTERED` additionally controls whether the **primary key** is a **clustered index**. If the keyword is not specified, it is controlled by the system variable `@@global.tidb_enable_clustered_index`, as described in [clustered indexes](https://docs.pingcap.com/zh/tidb/stable/clustered-indexes). +> - In TiDB: A **primary key** is unique and is not null. But the primary key is not guaranteed to be a **clustered index**. Instead, another set of keywords `CLUSTERED` / `NONCLUSTERED` additionally controls whether the **primary key** is a **clustered index**. If the keyword is not specified, it is controlled by the system variable `@@global.tidb_enable_clustered_index`, as described in [clustered indexes](https://docs.pingcap.com/tidb/stable/clustered-indexes). The **primary key** is defined in the `CREATE TABLE` statement. The [primary key constraint](/constraints.md#primary-key) requires that all constrained columns contain only non-NULL values. diff --git a/develop/dev-guide-insert-data.md b/develop/dev-guide-insert-data.md index 595cc4fb0c5f1..4d6686725b133 100644 --- a/develop/dev-guide-insert-data.md +++ b/develop/dev-guide-insert-data.md @@ -290,7 +290,7 @@ There are two solutions to handle this error: INSERT INTO `bookshop`.`users` (`balance`, `nickname`) VALUES (0.00, 'nicky'); ``` -- If you are sure that you **_must_** specify this column, then you can use the [`SET` statement](https://docs.pingcap.com/zh/tidb/stable/sql-statement-set-variable) to allow the column of `AUTO_RANDOM` to be specified during insertion time by changing the user variable. +- If you are sure that you **_must_** specify this column, then you can use the [`SET` statement](https://docs.pingcap.com/tidb/stable/sql-statement-set-variable) to allow the column of `AUTO_RANDOM` to be specified during insertion time by changing the user variable. {{< copyable "sql" >}} diff --git a/develop/dev-guide-playground-gitpod.md b/develop/dev-guide-playground-gitpod.md index e1c1409f2ea66..6daa910bc56d2 100644 --- a/develop/dev-guide-playground-gitpod.md +++ b/develop/dev-guide-playground-gitpod.md @@ -33,7 +33,7 @@ After that, you will see a page similar to the following: ![playground gitpod workspace init](/media/develop/playground-gitpod-workspace-init.png) -This scenario in the page uses [TiUP](https://docs.pingcap.com/zh/tidb/stable/tiup-overview) to build a TiDB Playground. You can check the progress on the left side of the terminal area. +This scenario in the page uses [TiUP](https://docs.pingcap.com/tidb/stable/tiup-overview) to build a TiDB Playground. You can check the progress on the left side of the terminal area. Once the TiDB Playground is ready, another `Spring JPA Hibernate` task will run. You can check the progress on the right side of the terminal area. diff --git a/dm/task-configuration-file-full.md b/dm/task-configuration-file-full.md index fbae911ba00d1..6d4ddbc86352c 100644 --- a/dm/task-configuration-file-full.md +++ b/dm/task-configuration-file-full.md @@ -126,7 +126,7 @@ loaders: # The import mode during the full import phase. The following modes are supported: # - "logical" (default). Uses TiDB Lightning's logical import mode to import data. Document: https://docs.pingcap.com/tidb/stable/tidb-lightning-logical-import-mode - # - "physical". Uses TiDB Lightning's physical import mode to import data. Document: https://docs.pingcap.com/zh/tidb/stable/tidb-lightning-physical-import-mode + # - "physical". Uses TiDB Lightning's physical import mode to import data. Document: https://docs.pingcap.com/tidb/stable/tidb-lightning-physical-import-mode # The "physical" mode is still an experimental feature and is not recommended in production. import-mode: "logical" # Methods to resolve conflicts in logical import. diff --git a/migrate-large-mysql-shards-to-tidb.md b/migrate-large-mysql-shards-to-tidb.md index b5f3513e322f6..887c06776f550 100644 --- a/migrate-large-mysql-shards-to-tidb.md +++ b/migrate-large-mysql-shards-to-tidb.md @@ -281,7 +281,7 @@ name: task-test # The name of the task. Should be globally unique. task-mode: incremental # The mode of the task. "incremental" means full data migration is skipped and only incremental replication is performed. # Required for incremental replication from sharded tables. By default, the "pessimistic" mode is used. # If you have a deep understanding of the principles and usage limitations of the optimistic mode, you can also use the "optimistic" mode. -# For more information, see [Merge and Migrate Data from Sharded Tables](https://docs.pingcap.com/zh/tidb/dev/feature-shard-merge/). +# For more information, see [Merge and Migrate Data from Sharded Tables](https://docs.pingcap.com/tidb/dev/feature-shard-merge/). shard-mode: "pessimistic" diff --git a/placement-rules-in-sql.md b/placement-rules-in-sql.md index 8203cf7005a34..cc487746bb00a 100644 --- a/placement-rules-in-sql.md +++ b/placement-rules-in-sql.md @@ -30,7 +30,7 @@ With the Placement Rules in SQL feature, you can [create placement policies](#cr > **Tip:** > -> The implementation of *Placement Rules in SQL* relies on the *placement rules feature* of PD. For details, refer to [Configure Placement Rules](https://docs.pingcap.com/zh/tidb/stable/configure-placement-rules). In the context of Placement Rules in SQL, *placement rules* might refer to *placement policies* attached to other objects, or to rules that are sent from TiDB to PD. +> The implementation of *Placement Rules in SQL* relies on the *placement rules feature* of PD. For details, refer to [Configure Placement Rules](https://docs.pingcap.com/tidb/stable/configure-placement-rules). In the context of Placement Rules in SQL, *placement rules* might refer to *placement policies* attached to other objects, or to rules that are sent from TiDB to PD. ## Limitations diff --git a/tidb-resource-control.md b/tidb-resource-control.md index 0b97e03419c31..547228739ba2b 100644 --- a/tidb-resource-control.md +++ b/tidb-resource-control.md @@ -159,9 +159,9 @@ You can view the [Resource Manager page](/dashboard/dashboard-resource-manager.m -For TiDB Self-Managed, you can use the [`CALIBRATE RESOURCE`](https://docs.pingcap.com/zh/tidb/stable/sql-statement-calibrate-resource) statement to estimate the cluster capacity. +For TiDB Self-Managed, you can use the [`CALIBRATE RESOURCE`](https://docs.pingcap.com/tidb/stable/sql-statement-calibrate-resource) statement to estimate the cluster capacity. -For TiDB Cloud, the [`CALIBRATE RESOURCE`](https://docs.pingcap.com/zh/tidb/stable/sql-statement-calibrate-resource) statement is inapplicable. +For TiDB Cloud, the [`CALIBRATE RESOURCE`](https://docs.pingcap.com/tidb/stable/sql-statement-calibrate-resource) statement is inapplicable.