-
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
executor: check unequal handles when buildTableReader4INLJoin #15675
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.
LGTM
Codecov Report
@@ Coverage Diff @@
## master #15675 +/- ##
================================================
+ Coverage 80.4243% 80.4643% +0.0399%
================================================
Files 504 504
Lines 134473 135086 +613
================================================
+ Hits 108149 108696 +547
- Misses 17833 17921 +88
+ Partials 8491 8469 -22 |
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 |
Signed-off-by: sre-bot <sre-bot@pingcap.com>
cherry pick to release-3.0 in PR #15734 |
Signed-off-by: sre-bot <sre-bot@pingcap.com>
cherry pick to release-3.1 in PR #15735 |
cherry pick to release-4.0 in PR #15736 |
What problem does this PR solve?
Issue Number: close #15658
Problem Summary:
Before this commit, buildTableReaderForIndexJoin assumes that there is only one value for handles in lookupContent. Thus we'll fetch redundant rows.
What is changed and how it works?
Proposal: xxx
What's Changed:
Check whether there are redundant unequal
handle
values in buildTableReaderForIndexJoin.How it Works:
Related changes
Check List
Tests
Side effects
Release note