Incremental restore: fix the issue that backfill data is not covered by newTS

[3pointer]

What problem does this PR solve?

Issue Number: close #54426

Problem Summary:
see #54426 (comment)

What changed and how does it work?

make sure the rewritten data cover the backfilled data.

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.

 fix the issue that backfill ddls(add index/modify column) may not restored correctly during incremental restore.

[ti-chi-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[tiprow]

Hi @3pointer. 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-sigs/prow repository.

[3pointer]

/ok-to-test

[codecov]

Codecov Report

Attention: Patch coverage is 70.00000% with 3 lines in your changes missing coverage. Please review.

Project coverage is 56.8457%. Comparing base (22f9a3b) to head (ce345a0).
Report is 875 commits behind head on master.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #54430         +/-   ##
=================================================
- Coverage   72.8182%   56.8457%   -15.9726%     
=================================================
  Files          1536       1664        +128     
  Lines        435896     612938     +177042     
=================================================
+ Hits         317412     348429      +31017     
- Misses        98850     240715     +141865     
- Partials      19634      23794       +4160     

Flag	Coverage Δ
integration	38.4186% <70.0000%> (?)
unit	71.9880% <0.0000%> (+0.1618%)	⬆️

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

Components	Coverage Δ
dumpling	52.9656% <ø> (ø)
parser	∅ <ø> (∅)
br	62.8616% <70.0000%> (+16.7973%)	⬆️

[3pointer]

/ok-to-test

[3pointer]

/ok-to-test

[Leavrth]

It may be worth noting that
Restore GC Safepoint TS < DDL ts < Incremental kv Rewrite ts

[3pointer]

/test pull-br-integration-test

[tiprow]

@3pointer: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test fast_test_tiprow
• /test tidb_parser_test

Use /test all to run all jobs.

In response to this:

/test pull-br-integration-test

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-sigs/prow repository.

[3pointer]

/test check-dev2

[tiprow]

@3pointer: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test fast_test_tiprow
• /test tidb_parser_test

Use /test all to run all jobs.

In response to this:

/test check-dev2

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-sigs/prow repository.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Leavrth, YuJuncen

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/OWNERS [Leavrth,YuJuncen]

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:

• 2024-07-05 03:24:45.232298156 +0000 UTC m=+1554011.717786987: ☑️ agreed by Leavrth.
• 2024-07-05 09:19:25.884658426 +0000 UTC m=+3663.119892541: ☑️ agreed by YuJuncen.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.5: #54505.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-8.1: #54997.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.5: #55656.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.1: #56904.