-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Wrong query results for filters that involve partition columns and data file columns and pushdown_filters
is enabled
#15912
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
Comments
sounds serious |
pushdown_filters
is enabled
This is all the more reason I think to avoid adding more complexity to ListingTable as we are disucssing in |
I think the fix is relatively simple though: any filters that reference both partition columns and data columns need to be marked as Inexact. I'm traveling so don't know that I can make a PR soon but it's a couple LOC. |
Also although yes this is serious I suspect is pretty rare to have a filter that depends on both a partition column and data column. It hasn't been reported for years... |
I also think it is not that common to turn on filter_pushdown and use it with ListingTable - e.g. InfluxData and Comet both do not use ListingTable 🤔 |
Good point |
Describe the bug
Filters such as
partition_col = col_from_file
are never applied ifdatafusion.execution.parquet.pushdown_filters = true
To Reproduce
With
datafusion-cli
:Which is clearly wrong.
Expected behavior
Additional context
No response
The text was updated successfully, but these errors were encountered: