-
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: fix incorrect result for != all (subq)
#19576
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
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
Your auto merge job has been accepted, waiting for:
|
/run-all-tests |
/run-all-tests |
@eurekaka merge failed. |
/merge |
Your auto merge job has been accepted, waiting for:
|
/run-all-tests |
@eurekaka merge failed. |
/run-all-tests |
Signed-off-by: ti-srebot <[email protected]>
cherry pick to release-4.0 in PR #19831 |
Signed-off-by: ti-srebot <[email protected]> Co-authored-by: Kenan Yao <[email protected]>
What problem does this PR solve?
Issue Number: close #19423
Problem Summary:
Incorrect result returned a kind of anti-semi-join.
What is changed and how it works?
What's Changed:
One kind of cases are fixed by #19472, but another kind of anti-semi-joins built from
!= all (subq)
still have problems.How it Works:
Make a copy of
Column
before modifyingInOperand
.Related changes
Check List
Tests
Side effects
N/A
Release note
!= all (subq)
.