backkem commented on issue #8699: URL: https://github.com/apache/arrow-datafusion/issues/8699#issuecomment-1884978887
I had made a suggestion [here](https://github.com/apache/arrow-datafusion/issues/970#issuecomment-1793381505) that turns the current approach around: instead of a `TableProvider` expressing what it can push down. Let the `TableProvider` run it's own optimizer pass on (part of) the plan to self-determine what it can push down; replacing its federated part of the plan with a virtual TableScan. In the comment I linked I provided some references to the Presto codebase taking this approach. -- 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]
