[SPARK-32721][SQL][FOLLOWUP] Simplify if clauses with null and boolean #29603
Conversation
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
|
cc @dbtsai |
cloud-fan
approved these changes
Sep 1, 2020
viirya
approved these changes
Sep 1, 2020
dbtsai
reviewed
Sep 1, 2020
| case If(cond, l @ Literal(null, _), FalseLiteral) if !cond.nullable => And(cond, l) | ||
| case If(cond, l @ Literal(null, _), TrueLiteral) if !cond.nullable => Or(Not(cond), l) | ||
| case If(cond, FalseLiteral, l @ Literal(null, _)) if !cond.nullable => And(Not(cond), l) | ||
| case If(cond, TrueLiteral, l @ Literal(null, _)) if !cond.nullable => Or(cond, l) |
There was a problem hiding this comment.
minor, can we call l as nullLiteral?
case If(cond, nullLiteral @ Literal(null, _), FalseLiteral) if !cond.nullable => And(cond, nullLiteral)
case If(cond, nullLiteral @ Literal(null, _), TrueLiteral) if !cond.nullable => Or(Not(cond), nullLiteral)
case If(cond, FalseLiteral, nullLiteral @ Literal(null, _)) if !cond.nullable => And(Not(cond), nullLiteral)
case If(cond, TrueLiteral, nullLiteral @ Literal(null, _)) if !cond.nullable => Or(cond, nullLiteral)
There was a problem hiding this comment.
Hmm that will break each of these into two lines which may affect readability, also I think given these are already Literal(null, _), naming the variable to nullLiteral doesn't add much value maybe?
dbtsai
reviewed
Sep 1, 2020
| assertEquivalent(If(p, nullLiteral, FalseLiteral), And(p, nullLiteral)) | ||
| assertEquivalent(If(p, nullLiteral, TrueLiteral), Or(IsNotNull('a), nullLiteral)) | ||
| assertEquivalent(If(p, FalseLiteral, nullLiteral), And(IsNotNull('a), nullLiteral)) | ||
| assertEquivalent(If(p, TrueLiteral, nullLiteral), Or(IsNull('a), nullLiteral)) |
There was a problem hiding this comment.
minor, make it consistent with the first test. Either we use p for IsNull('a) or in first test, we use IsNull('a).
|
Test build #128124 has finished for PR 29603 at commit
|
|
Merged into master. Thanks @sunchao @cloud-fan @viirya |
|
Test build #128136 has finished for PR 29603 at commit
|
holdenk
pushed a commit
to holdenk/spark
that referenced
this pull request
Oct 27, 2020
### What changes were proposed in this pull request? This is a follow-up on SPARK-32721 and PR apache#29567. In the previous PR we missed two more cases that can be optimized: ``` if(p, false, null) ==> and(not(p), null) if(p, true, null) ==> or(p, null) ``` ### Why are the changes needed? By transforming if to boolean conjunctions or disjunctions, we can enable more filter pushdown to datasources. ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? Added unit tests. Closes apache#29603 from sunchao/SPARK-32721-2. Authored-by: Chao Sun <[email protected]> Signed-off-by: DB Tsai <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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 on SPARK-32721 and PR #29567. In the previous PR we missed two more cases that can be optimized:
Why are the changes needed?
By transforming if to boolean conjunctions or disjunctions, we can enable more filter pushdown to datasources.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Added unit tests.