-
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
*: refactoring the code of batchChecker #12108
*: refactoring the code of batchChecker #12108
Conversation
batchChecker is difficult to maintain, we should get rid of it. In this commit I catch the BatchGet result into the snapshot, in this way we can achieve the same goal as the batchChecker
Codecov Report
@@ Coverage Diff @@
## master #12108 +/- ##
===========================================
Coverage 81.5473% 81.5473%
===========================================
Files 449 449
Lines 97124 97124
===========================================
Hits 79202 79202
Misses 12317 12317
Partials 5605 5605 |
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 |
/run-all-tests |
/rebuild |
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, so update, replace also need do same thing?
Yes, if we want to remove the batchChecker totally. @lysu |
/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
cherry pick to release-3.0 failed |
It seems that, not for sure, we failed to cherry-pick this commit to release-3.0. Please comment '/run-cherry-picker' to try to trigger the cherry-picker if we did fail to cherry-pick this commit before. @tiancaiamao PTAL. |
What problem does this PR solve?
The
batchChecker
is difficult to maintain, we should try to get rid of it.Expect:
Get:
What is changed and how it works?
The first step: do not use it.
The second step: clean up the code.
In this commit, I catch the BatchGet result into the snapshot, in this way we can achieve the same goal as the
batchChecker
I re-implement the
insert ... on duplicate key update ...
without using thebatchChecker
.Check List
Tests
Side effects
Related changes
Release note
Fix bugs of
insert ... on duplicate update
on the partitioned table