adriangb commented on PR #15566: URL: https://github.com/apache/datafusion/pull/15566#issuecomment-2812614956
> Yep, I've noticed that too, but how those plans didn't change before? We were trying to pushdown filters over RepartitionExec's and CoalesceBatches I'm not sure. The flow before was: 1. Recurse down with filters from parents `x = 5` (example). 1. Hit a FilterExec. It says it's okay to push down `x = 5`. 1. Pass through CoalesceBatchesExec. 1. Hit a scan that says it can't absorb the filters and returns `Unsupported`. 1. Recurse back up to the `FilterExec`. 1. Ask the `FilterExec` if it can handle `x = 5` itself. 1. FilterExec says yes, it replaces itself with a new `FilterExec`. The story is the same if there are no filters from parents except for the last two steps which are skipped and the plan is unmodified. -- 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...@datafusion.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org For additional commands, e-mail: github-h...@datafusion.apache.org
