Closed lyzx2001 closed 7 months ago
Merging #46763 (cfb7250) into master (cc42e4b) will increase coverage by
0.3830%
. Report is 1 commits behind head on master. The diff coverage is50.5376%
.
/cc @lance6716
/retest
/retest
/test pull-br-integration-test
@lance6716: The specified target(s) for /test
were not found.
The following commands are available to trigger required jobs:
/test tiprow_fast_test
Use /test all
to run all jobs.
/test pull-br-integration-test
@lyzx2001: The specified target(s) for /test
were not found.
The following commands are available to trigger required jobs:
/test tiprow_fast_test
Use /test all
to run all jobs.
/retest
/test pull-br-integration-test
@lance6716: The specified target(s) for /test
were not found.
The following commands are available to trigger required jobs:
/test tiprow_fast_test
Use /test all
to run all jobs.
/test pull-br-integration-test
@lyzx2001: The specified target(s) for /test
were not found.
The following commands are available to trigger required jobs:
/test tiprow_fast_test
Use /test all
to run all jobs.
/retest
/retest
/cc @lance6716
/retest
/retest
/test pull-br-integration-test
/test pull-br-integration-test
@lyzx2001: The specified target(s) for /test
were not found.
The following commands are available to trigger required jobs:
/test tiprow_fast_test
Use /test all
to run all jobs.
/test pull-br-integration-test
@lyzx2001: The specified target(s) for /test
were not found.
The following commands are available to trigger required jobs:
/test tiprow_fast_test
Use /test all
to run all jobs.
/test pull-br-integration-test
@lyzx2001: The specified target(s) for /test
were not found.
The following commands are available to trigger required jobs:
/test tiprow_fast_test
Use /test all
to run all jobs.
/test pull-br-integration-test
@lyzx2001: The specified target(s) for /test
were not found.
The following commands are available to trigger required jobs:
/test tiprow_fast_test
Use /test all
to run all jobs.
/test pull-br-integration-test
@lance6716: The specified target(s) for /test
were not found.
The following commands are available to trigger required jobs:
/test tiprow_fast_test
Use /test all
to run all jobs.
/test pull-br-integration-test
@lyzx2001: The specified target(s) for /test
were not found.
The following commands are available to trigger required jobs:
/test tiprow_fast_test
Use /test all
to run all jobs.
/test pull-br-integration-test
@lyzx2001: The specified target(s) for /test
were not found.
The following commands are available to trigger required jobs:
/test tiprow_fast_test
Use /test all
to run all jobs.
/test all
/test pull-br-integration-test
@lyzx2001: The specified target(s) for /test
were not found.
The following commands are available to trigger required jobs:
/test tiprow_fast_test
Use /test all
to run all jobs.
/test pull-br-integration-test
@lyzx2001: The specified target(s) for /test
were not found.
The following commands are available to trigger required jobs:
/test tiprow_fast_test
Use /test all
to run all jobs.
/test pull-br-integration-test
@lyzx2001: The specified target(s) for /test
were not found.
The following commands are available to trigger required jobs:
/test tiprow_fast_test
Use /test all
to run all jobs.
/cc @D3Hunter
/test pull-br-integration-test
@lyzx2001: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test
message.
/test pull-br-integration-test
@lyzx2001: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test
message.
/test pull-br-integration-test
@lyzx2001: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test
message.
/retest
@lyzx2001: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test
message.
What problem does this PR solve?
Issue Number: close #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 https://github.com/pingcap/tidb/pull/45926
This PR contains the algorithms for data KV checking.
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
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.