-
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 column ddl error #8545
Conversation
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.
Mostly LGTM, please address comment.
2e7e0f3
to
24c44b8
Compare
@crazycs520 PTAL |
24c44b8
to
1f25c29
Compare
@crazycs520 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.
7f323ce
to
d19b237
Compare
Please resolve the conflicts. |
8010fa6
to
e773c46
Compare
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.
LGTM
/run-all-tests |
What problem does this PR solve?
Releate PR #8171 , The old tidb version cancels the drop of the column, which may cause the column state to be neither
StatePublic
norStateNone
. For the client, the column is not visible, but adding a column with the same name to the client will fail because the name of the "column" column already exists.What is changed and how it works?
We can only cancel drop column job when the column state is on
StatePublic
, otherwise, cancel column and make the column state rollback to public may cause data consistency.Check List
Side effects
Related changes
This change is