Uh oh!
There was an error while loading. Please reload this page.
[SPARK-36665][SQL][FOLLOWUP] Avoid Optimizing Not(InSubquery) - #35400
Closed
kazuyukitanimura wants to merge 2 commits into
Closed
[SPARK-36665][SQL][FOLLOWUP] Avoid Optimizing Not(InSubquery)#35400kazuyukitanimura wants to merge 2 commits into
kazuyukitanimura wants to merge 2 commits into
Conversation
kazuyukitanimura
commented
Feb 5, 2022
ContributorAuthor
@aokolnychyi Thank you for finding the issue. cc @viirya |
viirya
commented
Feb 5, 2022
Member
cc @cloud-fan |
viirya
reviewed
Feb 5, 2022
Uh oh!
There was an error while loading. Please reload this page.
viirya
reviewed
Feb 5, 2022
HyukjinKwon
commented
Feb 7, 2022
Member
cc @allisonwang-db FYI |
cloud-fan
commented
Feb 7, 2022
Contributor
Are there any real-world examples to demonstrate the effectiveness of the rule |
kazuyukitanimura
commented
Feb 7, 2022
ContributorAuthor
Thanks @cloud-fan My goal here is to unblock #35395. As you mentioned your concern about the complexity of this logic, I opened #35428 to remove For the effectiveness, I put many examples at that helps simplifying users' queries. |
kazuyukitanimura
commented
Feb 7, 2022
ContributorAuthor
Closing by preferring #35428 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
This is a follow-up PR to fix the bug introduced by SPARK-36665. With this fix,
NotPropagationoptimization does not apply toInSubquerycases.Why are the changes needed?
NotPropagationoptimization previously brokeRewritePredicateSubqueryso that it does not properly rewrite the predicate to a NULL-aware left anti join anymore.Does this PR introduce any user-facing change?
No
How was this patch tested?
Unit test added