-
Notifications
You must be signed in to change notification settings - Fork 131
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
drainer: bugfix, handle "missing column" when a column is getting dropped #803
Conversation
/run-integration-tests |
2 similar comments
/run-integration-tests |
/run-integration-tests |
df35218
to
4c2d821
Compare
/run-integration-tests |
/run-unit-tests |
LGTM now |
c1b01d9
to
867b525
Compare
280596c
to
8cc56d0
Compare
/run-all-tests |
3 similar comments
/run-all-tests |
/run-all-tests |
/run-all-tests |
64bee3d
to
d260115
Compare
/run-all-tests |
/run-unit-tests |
/run-all-tests |
1 similar comment
/run-all-tests |
99c6ed1
to
41e7386
Compare
/run-all-tests |
@suzaku pls fix the conflicts. |
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
Note after added the one more ddl binlog event, with the new version tidb, the old version pump
will or will not execute the ddl(when receiving the newly added binlog event)
LGTM |
need to add release note, and update upgrade document(may not compatible with old tidb?) |
|
/run-cherry-picker |
cherry pick to release-2.1 failed |
cherry pick to release-3.0 failed |
What problem does this PR solve?
DML binlogs may be wrong if there's a concurrent
drop column
DDL running.The column being dropped may be missing before the corresponding DDL binlog reached drainer, because TiDB stops sending the dropped column starting from the DeleteOnly state.
What is changed and how it works?
Check List
Tests
Code changes
Side effects
Related changes