-
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: fix failure to update BIT columns with downstream TiDB when message passes through Kafka #667
Conversation
…[]byte data to uint64 in tranlate.go to avoid issue tidb#10988 3. rename the table a to binlog_case3 to make it easy to check later
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.
please fix ci, you can run "make check" locally
/rebuild |
/run-all-tests |
/run-all-tests |
/run-all-tests |
/run-all-tests |
/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
@suzaku PTAL
All comments have been revised. PTAL. @suzaku |
/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.
Great, LGTM.
What problem does this PR solve?
Issue TOOL-1374, which is caused by pingcap/tidb#10988
What is changed and how it works?
Encode BIT types as integers instead of byte strings. Since the longest value is BIT(64), it is safe to always convert as uint64.
Check List
Tests
Code changes
Side effects
Related changes