br: rebase auto random id if the table is common handle

[Leavrth]

What problem does this PR solve?

Issue Number: close #52255

Problem Summary:
the auto_rand_base of table with common handle isn't be rebased by BR.

What changed and how does it work?

rebase the auto_rand_base of table with common handle

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.

[YuJuncen]

You may add a simple test case at br_views_and_sequences or br_incompatible_tidb_config

[codecov]

Codecov Report

Merging #52256 (8cbb2fa) into master (7b8fd37) will decrease coverage by 1.6032%.
Report is 47 commits behind head on master.
The diff coverage is 0.0000%.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #52256        +/-   ##
================================================
- Coverage   72.3907%   70.7875%   -1.6033%     
================================================
  Files          1486       1547        +61     
  Lines        365580     455432     +89852     
================================================
+ Hits         264646     322389     +57743     
- Misses        81378     112527     +31149     
- Partials      19556      20516       +960     

Flag	Coverage Δ
integration	28.6223% <0.0000%> (?)
unit	70.9580% <0.0000%> (-1.3237%)	⬇️

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

Components	Coverage Δ
dumpling	53.9957% <ø> (-2.3014%)	⬇️
parser	∅ <ø> (∅)
br	33.6614% <0.0000%> (-12.6807%)	⬇️

[Leavrth]

You may add a simple test case at br_views_and_sequences or br_incompatible_tidb_config

Yes, I thinks it's the best way to merge these kind of cases into one script. Because it saves time for cluster restart. However, it makes things more complicated in the current scripts framework. Therefore, I would open a new script.

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

[BornChanger]

/cc @tangenta plta.

[ti-chi-bot]

@YuJuncen: Your lgtm message is repeated, so it is ignored.

In response to this:

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: tangenta, 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 [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-03-30 14:57:32.854225664 +0000 UTC m=+110314.381766207: ☑️ agreed by YuJuncen.
• 2024-04-01 09:44:43.49837833 +0000 UTC m=+264345.025918876: ☑️ agreed by tangenta.

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

/hold

[Leavrth]

/unhold

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

/ok-to-test

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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