Lordworms commented on PR #9314: URL: https://github.com/apache/arrow-datafusion/pull/9314#issuecomment-1962238226
> Could you help me to understand the impact of this change? From what I can tell, `ParquetFormat::create_physical_plan()` already checks this config before passing in the optional predicate, so this check seems redundant? Unless the intention is to centralize this check within `ParquetExec::new()` itself? Yes, what I get from this issue is that @SteveLauC wants to centralize this check with ParquetExec::new() -- 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: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
