-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
br: modify tables that should be altered auto id or random id #33719
Conversation
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
/cc @joccau |
/cc @3pointer |
1 similar comment
/cc @3pointer |
Code Coverage Details: https://codecov.io/github/pingcap/tidb/commit/0ce3ce6064b196d04d7107acc299ab1fd46eff99 |
I think we need another test case to cover this change. |
/component br |
Rest LGTM. |
/run-integration-br-test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rest LGTM
/run-integration-br-test |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 8eb8be3
|
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
cherry pick to release-4.0 in PR #33984 |
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
cherry pick to release-5.0 in PR #33985 |
cherry pick to release-5.1 failed |
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
cherry pick to release-5.2 in PR #33986 |
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
cherry pick to release-5.3 in PR #33987 |
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
cherry pick to release-5.4 in PR #33988 |
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
cherry pick to release-6.0 in PR #33989 |
TiDB MergeCI notify
|
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
What problem does this PR solve?
Issue Number: close #33596
Problem Summary:
What is changed and how it works?
We modify tables that should be altered auto_increment or auto_random_base. Tables existed in restored cluster or created by executing ddl job all should be altered during incremental restoration.
As long as we alter auto_increment or auto_random_base in restored table, we can insert records successfully.
Check List
Tests
a
,b
,c
,d
,e
(NEXT_GLOBAL_ROW_ID is 1).b
,c
,d
(NEXT_GLOBAL_ROW_ID is 30001).b
,c
, drop tabled
, rename tablee
toe1
.a
,b
,e1
via one TiDB instance (NEXT_GLOBAL_ROW_ID is 30001).a
,b
,c
,d
,e
successfully, which is the correct result. In this situation,a
is the table changed NEXT_GLOBAL_ROW_ID,b
is the table truncated,c
is the table truncated and changed NEXT_GLOBAL_ROW_ID,d
is the table dropped,e1
is the table renamed and changed NEXT_GLOBAL_ROW_ID.Release note