From 6a00b92802f90cac752dccae3c0ba892005c8238 Mon Sep 17 00:00:00 2001 From: Ti Chi Robot Date: Tue, 10 Oct 2023 17:34:56 +0800 Subject: [PATCH] tidb-lightning: fix strategy number (#14998) (#15008) --- tidb-lightning/tidb-lightning-physical-import-mode-usage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tidb-lightning/tidb-lightning-physical-import-mode-usage.md b/tidb-lightning/tidb-lightning-physical-import-mode-usage.md index 4bbd8a43d3571..78aba0e72486f 100644 --- a/tidb-lightning/tidb-lightning-physical-import-mode-usage.md +++ b/tidb-lightning/tidb-lightning-physical-import-mode-usage.md @@ -87,7 +87,7 @@ For the complete configuration file, refer to [the configuration file and comman Conflicting data refers to two or more records with the same PK/UK column data. When the data source contains conflicting data, the actual number of rows in the table is different from the total number of rows returned by the query using unique index. -TiDB Lightning offers three strategies for detecting conflicting data: +TiDB Lightning offers the following strategies for detecting conflicting data: - `remove` (recommended): records and removes all conflicting records from the target table to ensure a consistent state in the target TiDB. - `none`: does not detect duplicate records. `none` has the best performance in the two strategies, but might lead to inconsistent data in the target TiDB.