Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tidb-lightning: fix strategy number (#14998) #15009

Merged
merged 4 commits into from
Oct 10, 2023
Merged

tidb-lightning: fix strategy number (#14998) #15009

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
f247906
Add temp.md
qiancai Oct 10, 2023
807d309
Delete temp.md
qiancai Oct 10, 2023
4d995cb
Update tidb-lightning-physical-import-mode-usage.md
qiancai Oct 10, 2023
1310db7
Update tidb-lightning/tidb-lightning-physical-import-mode-usage.md
qiancai Oct 10, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion tidb-lightning/tidb-lightning-physical-import-mode-usage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -79,7 +79,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.
Expand Down