tustvold opened a new issue, #2307: URL: https://github.com/apache/arrow-datafusion/issues/2307
**Is your feature request related to a problem or challenge? Please describe what you are trying to do.** This seems to be a very common source of bugs: * #2306 * #1939 * #2173 On a holistic level I can't see why it needs to be async, given it returns an async stream which can/should contain any deferred computations, as opposed to doing them synchronously with the plan's construction. **Describe the solution you'd like** I would like to make `ExecutionPlan::execute` sync **Describe alternatives you've considered** We could not do this **Additional context** The new scheduler has a slightly ugly hack to workaround this - https://github.com/apache/arrow-datafusion/pull/2226/files#diff-b3e57d18925cb116e868da5f997735bdf6f937d53635e85bc227c4e01a2e2b33R138 This will likely help with future work to de-asyncify the physical plan - see #2199 -- 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]
