br: fix duplicated table check would block incremental restore

[RidRisR]

What problem does this PR solve?

Issue Number: close #55562

Problem Summary:

BR would report unexpected BR:Restore:ErrTablesAlreadyExisted when incremental restore.

What changed and how does it work?

disable duplicated table check in incremental restore.

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

All modified and coverable lines are covered by tests ✅

Project coverage is 57.2883%. Comparing base (290dc46) to head (8b8162f).
Report is 40 commits behind head on master.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #55688         +/-   ##
=================================================
- Coverage   72.9295%   57.2883%   -15.6413%     
=================================================
  Files          1581       1714        +133     
  Lines        442365     626323     +183958     
=================================================
+ Hits         322615     358810      +36195     
- Misses        99938     243196     +143258     
- Partials      19812      24317       +4505     

Flag	Coverage Δ
integration	38.6079% <100.0000%> (?)
unit	72.0198% <0.0000%> (+0.0197%)	⬆️

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

Components	Coverage Δ
dumpling	52.9567% <ø> (ø)
parser	∅ <ø> (∅)
br	62.8016% <100.0000%> (+17.3468%)	⬆️

[RidRisR]

/test check-dev2

[RidRisR]

/test pull-br-integration-test

[RidRisR]

/test unit-test

[tiprow]

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

In response to this:

/test unit-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.

[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:

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

• 2024-09-03 07:45:30.056069289 +0000 UTC m=+344054.574122209: ☑️ agreed by Leavrth.
• 2024-09-03 11:29:28.342373363 +0000 UTC m=+357492.860426273: ☑️ agreed by BornChanger.

[tiprow]

@RidRisR: 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
tidb_parser_test	8b8162f	link	true	/test tidb_parser_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.