lightning: add complex unit tests for lightning post-import conflict detection "replace" mode

[lyzx2001]

What problem does this PR solve?

Issue Number: ref #45774

Problem Summary:

Currently lightning only supports "remove" mode for post-import conflict detection, but many customers request lightning to support "replace" mode for lightning post-import conflict detection.

We would like to support "replace" mode for lightning post-import conflict detection:
To resolve rows with conflict, instead of deleting all the rows that are engaged in conflict (the algorithm for remove), we delete some of the rows with conflict and reserve other rows that can be kept and not cause conflict anymore. Under this circumstance, we only delete the necessary rows to resolve conflicts, so that we can keep more original rows than remove mode as long as the conflicts are resolved.

The algorithms for index KV checking is contained in #45926

The algorithms for data KV checking is contained in #46763

The integration tests are contained in #47460

This PR contains complex unit tests to test the correctness and performance of the algorithms.

What is changed and how it works?

Demo code for 'replace' mode of lightning post-import conflict detection:

https://github.com/lyzx2001/tidb-conflict-replace

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[tiprow]

Hi @lyzx2001. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[codecov]

Codecov Report

Merging #48514 (1eb2953) into master (d2c0c6e) will increase coverage by 1.6709%.
Report is 138 commits behind head on master.
The diff coverage is n/a.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #48514        +/-   ##
================================================
+ Coverage   71.4920%   73.1630%   +1.6709%     
================================================
  Files          1402       1435        +33     
  Lines        406343     418251     +11908     
================================================
+ Hits         290503     306005     +15502     
+ Misses        96004      93366      -2638     
+ Partials      19836      18880       -956     

Flag	Coverage Δ
integration	44.1767% <ø> (?)
unit	71.6351% <ø> (+0.1430%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	54.1220% <ø> (+0.1345%)	⬆️
parser	∅ <ø> (∅)
br	49.0585% <ø> (-3.8596%)	⬇️

[lyzx2001]

/cc @lance6716

[lance6716]

Suggested change

	info, err := ddl.MockTableInfo(mockSctx, node[0].(*ast.CreateTableStmt), 1)
	info, err := ddl.MockTableInfo(mockSctx, node[0].(*ast.CreateTableStmt), 108)

and we can delete line 261.

Also for other tests

[lyzx2001]

/cc @D3Hunter

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: D3Hunter, lance6716

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• br/pkg/lightning/OWNERS [D3Hunter,lance6716]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2023-11-21 02:59:23.090254827 +0000 UTC m=+286791.755481022: ☑️ agreed by lance6716.
• 2023-11-22 06:39:45.57315498 +0000 UTC m=+386414.238381177: ☑️ agreed by D3Hunter.

[tiprow]

@lyzx2001: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
tiprow_fast_test	1eb2953	link	true	/test tiprow_fast_test

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.