-
Notifications
You must be signed in to change notification settings - Fork 283
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
mysql(ticdc): fix wrong dml order when batch DML is enabled (#8553) #8582
mysql(ticdc): fix wrong dml order when batch DML is enabled (#8553) #8582
Conversation
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
[REVIEW NOTIFICATION] This pull request has not been approved. 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. |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 75b8a28
|
/run-verify-tests |
Codecov Report
Additional details and impacted files
Flags with carried forward coverage won't be shown. Click here to find out more. @@ Coverage Diff @@
## release-6.1 #8582 +/- ##
================================================
Coverage ? 61.9550%
================================================
Files ? 1033
Lines ? 139690
Branches ? 0
================================================
Hits ? 86545
Misses ? 45888
Partials ? 7257 |
This is an automated cherry-pick of #8553
What problem does this PR solve?
Issue Number: close #8552
What is changed and how it works?
DML in one single transaction, keep the DML order: delete,update, insert
Check List
Tests
Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note