br: error out if pitr with table filter has exchange partition in/out filter range

[Tristan1900]

What problem does this PR solve?

Issue Number: close #59723

Problem Summary:

What changed and how does it work?

we detect partition changes during log restore, if we found a partition is moved in/out of the filter range during log restore, we throw an error since we cannot support on partition level right now. If the partition exchange happens totally in or out of the filter range without moving across the filter boundary, we can support that and no error will be thrown.

also added a few more tests to piggyback on this PR

1. filter restore one table at a time and don't clean up cluster
2. filter restore with log compaction
3. filter restore with truncation

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 @Tristan1900. 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.

[codecov]

Codecov Report

Attention: Patch coverage is 74.02597% with 20 lines in your changes missing coverage. Please review.

Project coverage is 74.8242%. Comparing base (0fc1412) to head (9fd164d).
Report is 41 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #59683        +/-   ##
================================================
+ Coverage   72.9943%   74.8242%   +1.8298%     
================================================
  Files          1697       1715        +18     
  Lines        468905     476017      +7112     
================================================
+ Hits         342274     356176     +13902     
+ Misses       105552      97907      -7645     
- Partials      21079      21934       +855     

Flag	Coverage Δ
integration	46.3125% <74.0259%> (?)
unit	72.3336% <0.0000%> (+0.1313%)	⬆️

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

Components	Coverage Δ
dumpling	52.6910% <ø> (ø)
parser	∅ <ø> (∅)
br	62.0293% <74.0259%> (+16.9273%)	⬆️

[Tristan1900]

/retest

[tiprow]

@Tristan1900: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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.

[Tristan1900]

/retest

[tiprow]

@Tristan1900: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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.

[Tristan1900]

/retest

[tiprow]

@Tristan1900: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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: BornChanger, Leavrth

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 [BornChanger,Leavrth]

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:

• 2025-02-28 07:14:48.41912308 +0000 UTC m=+599236.372281345: ☑️ agreed by Leavrth.
• 2025-02-28 08:30:57.373347278 +0000 UTC m=+603805.326505543: ☑️ agreed by BornChanger.

[BornChanger]

/test pull-br-integration-test

[tiprow]

@BornChanger: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

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.

[BornChanger]

/run tidb-parser-test

[ti-chi-bot]

@Tristan1900: 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
pull-br-integration-test	9fd164d	link	true	/test pull-br-integration-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-sigs/prow repository. I understand the commands that are listed here.