-
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
planner: handle other-conditions from subqueries correctly when constructing IndexJoin #25817
Conversation
[REVIEW NOTIFICATION] This pull request has been approved by:
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 |
1 similar comment
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 7df47a0
|
/merge |
Signed-off-by: ti-srebot <[email protected]>
cherry pick to release-5.0 in PR #25818 |
Signed-off-by: ti-srebot <[email protected]>
cherry pick to release-5.1 in PR #25819 |
What problem does this PR solve?
Issue Number: close #25799
Problem Summary: planner: handle other-conditions from subqueries correctly when constructing IndexJoin
What is changed and how it works?
When constructing IndexJoin, TiDB extracts equal expressions from other-conditions and converts them into eq-conditions to build hash keys.
If these equal expressions are from some
[not] in
sub-queries, this conversation may lead to wrong results sinceIndexJoin
cannot deal with NULL correctly in this case.This PR skips this conversation for equal expressions from
[not] in
sub-queries.Check List
Tests
Release note