From 9ca02c1e4217fca9062e4a9386b67f5591646d5e Mon Sep 17 00:00:00 2001 From: qiancai Date: Tue, 10 Oct 2023 14:22:27 +0800 Subject: [PATCH] Update tidb-lightning-physical-import-mode-usage.md --- 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 70171053ed992..782da76978349 100644 --- a/tidb-lightning/tidb-lightning-physical-import-mode-usage.md +++ b/tidb-lightning/tidb-lightning-physical-import-mode-usage.md @@ -83,7 +83,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 two 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.