[SPARK-24402] [SQL] Optimize In
expression when only one element in the collection or collection is empty
#21797
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?
Two new rules in the logical plan optimizers are added.
Collection
, thephysical plan will be optimized to
EqualTo
, so predicatepushdown can be used.
Collection
is empty, and the input is nullable, thelogical plan will be simplified to
TODO:
we should still allow predicate pushdown.
In
usingtableswitch
orlookupswitch
when the numbers of the categories are low, and they are
Int
,Long
.should do benchmark for using different set implementation for faster
query.
filter(if (condition) null else false)
can be optimized to false.How was this patch tested?
Couple new tests are added.