andygrove opened a new issue #784: URL: https://github.com/apache/arrow-datafusion/issues/784
**Is your feature request related to a problem or challenge? Please describe what you are trying to do.** When creating an execution context we already have some extension points such as `with_query_planner` and `with_physical_optimizer_rules` and I would like to extend this so that we can override the execution path when calling `collect`. **Describe the solution you'd like** When creating DataFrames from Ballista, I would like the user to be able to call `collect` directly on the DataFrame and have a way to make this call the Ballista execution context. If we can add a `with_query_executor` method to the DataFusion execution config then I think we can make this work. **Describe alternatives you've considered** One alternative would be to implement a Ballista-specific implementation of the DataFrame trait. It would mostly just delegate to the DataFusion DataFrame except for execution methods such as `collect`. **Additional context** None -- 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]
