alamb commented on issue #4020:
URL: 
https://github.com/apache/arrow-datafusion/issues/4020#issuecomment-1311941688

   I have confirmed that what is displayed as `predicate` is really the 
`PruningPredicate` not the pushed down filters
   
   
https://github.com/apache/arrow-datafusion/blob/f2f846512ab032845de5dcee768a8a69ddf17eac/datafusion/core/src/physical_plan/file_format/parquet.rs#L304-L313
   
   While reviewing the code I think there is a real limitation as well which is 
that we only push down filter expressions into the parquet scan ONLY if we 
could make a pruning predicate (which is a much more limited set)
   
   I think what we should do to fix this issue is: 
   1. Change the display name from `predicate` to `pruning_predicate`
   2. Push down the filter that is passed to `ParquetExec::new()` rather than 
just the pruning predicate. 
   
   


-- 
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]

Reply via email to