-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Reduce duplicate Projection when PARQUET_PUSHDOWN_FILTERS is on. #4398
Comments
@alamb @tustvold @thinkharderdev Look forward to hearing your opinion😄 |
I think this relates to #4020, which appears to have been closed?! |
So if I understand correctly, you are saying we should push down the predicate so that we only used it to generate a row selection for the other rows (i.e. we do not buffer the predicate column in memory after we have generated the selection)? |
Would this be accomplished by simply making the filter pushdown exact? Or is there something else required? |
Ah yes, I misread the ticket #4028 may resolve this, although it might need an additional optimisation pass to remove the now-redundant projection |
Yes just like you mentioned it is an exact filter.
Sounds like a reasonable solution,seems miss this part in row filter. |
If the parquet pushdown filtering is indeed exact, returning |
I think it should work as is. As long and |
Is your feature request related to a problem or challenge? Please describe what you are trying to do.
In this sql will have two related cols:
1.
Selected
coll_orderkey
2.
Filter
coll_extendedprice
IMO, this situation where
Filter Col
not exists inSelected col
, is perfect for row_filter_push_down. We can only visit theFilter Col
once, without using theselection
do the decoding thing.Describe the solution you'd like
Maybe we can change the physical plan to
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: