-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
ddl: fix cancel drop index error #8504
Conversation
/run-all-tests |
@crazycs520 Please add proper label. |
/run-all-tests |
/run-all-tests |
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.
LGTM
/run-all-tests |
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.
LGTM
6027b18
to
fd9864d
Compare
@zimulala PTAL |
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.
LGTM
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.
@crazycs520 Please solve the CI error.
/run-all-tests |
What problem does this PR solve?
releate PR #8171
This PR make cancel drop index work correctly. Old tidb version cancel drop index may cause the index states neither on
StatePublic
norStateNone
. For client, the index is not visible, but client add index with the same name will fail because the name of 'xxx' index is already exists.What is changed and how it works?
We can only cancel drop index job when the index state is on
StatePublic
orStateWriteOnly
, otherwise, cancel index and make the index state rollback to public may cause data consistency.Check List
Tests
Code changes
Side effects
Related changes
This change is