br: skip some warning during restore system schemas

[Leavrth]

What problem does this PR solve?

Issue Number: ref #46527 Close #49394

Problem Summary:
some errors can be skipped.

What changed and how does it work?

skip the error

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

[Leavrth]

/test pull-br-integration-test

[tiprow]

@Leavrth: 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/test-infra repository.

[codecov]

Codecov Report

Merging #49385 (f7e9f60) into master (ba55c98) will increase coverage by 2.0848%.
Report is 95 commits behind head on master.
The diff coverage is 78.5714%.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #49385        +/-   ##
================================================
+ Coverage   71.0537%   73.1385%   +2.0848%     
================================================
  Files          1368       1425        +57     
  Lines        401803     434549     +32746     
================================================
+ Hits         285496     317823     +32327     
- Misses        96449      96902       +453     
+ Partials      19858      19824        -34     

Flag	Coverage Δ
integration	47.9844% <78.5714%> (?)
unit	71.0553% <ø> (+0.0015%)	⬆️

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

Components	Coverage Δ
dumpling	53.9663% <ø> (ø)
parser	∅ <ø> (∅)
br	57.0517% <78.5714%> (+4.0929%)	⬆️

[Leavrth]

/test pull-br-integration-test

[tiprow]

@Leavrth: 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/test-infra repository.

[Leavrth]

/test pull-br-integration-test

[tiprow]

@Leavrth: 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/test-infra repository.

[Leavrth]

error during merging temporary tables into system tables, table: tidb_mdl_view: [BR:Common:ErrUnknown]failed to execute REPLACE INTO mysql.tidb_mdl_view(job_id,db_name,table_name,query,session_id,txnstart,sql_digests) SELECT job_id,db_name,table_name,query,session_id,txnstart,sql_digests FROM __tidb_br_temporary_mysql.tidb_mdl_view ;: replace into view tidb_mdl_view is not supported now

[Leavrth]

/test pull-br-integration-test

[tiprow]

@Leavrth: 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/test-infra repository.

[Leavrth]

/retest

[tiprow]

@Leavrth: 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/test-infra repository.

[Leavrth]

/test pull-br-integration-test

[tiprow]

@Leavrth: 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/test-infra repository.

[Leavrth]

/retest

[tiprow]

@Leavrth: 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/test-infra repository.

[Leavrth]

/retest

[tiprow]

@Leavrth: 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/test-infra repository.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 3pointer, 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 [3pointer,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:

• 2023-12-12 09:35:53.283276551 +0000 UTC m=+348844.320503462: ☑️ agreed by 3pointer.
• 2023-12-21 05:29:14.353063482 +0000 UTC m=+1111645.390290409: ☑️ agreed by YuJuncen.