LiaCastaneda commented on issue #17527: URL: https://github.com/apache/datafusion/issues/17527#issuecomment-3284262157
> Yep that's the case. For example Parquet may not be able to fully evaluate the filter for each row but may still be able to use it for file level and row group stats pruning. Ah, I didn't acocunt for that > Expand the pushdown result enum from two yes/no cases to three cases: exact (parent can drop the filter), inexact (parent should still apply the filter but it may be referenced for stats/partial pruning) and unsupported (the filter is not going to be used at all). maybe we could start with this? although the subscriber option would still be interesting, especially now that we’re considering multiple filter types, a scan node could subscribe to just the type of filter it supports 🤔 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
