metesynnada commented on issue #4426:
URL:
https://github.com/apache/arrow-datafusion/issues/4426#issuecomment-1335100942
My first understanding is that
- We can utilize new LogicalPlan enums with name
- `CreatePlan`
- `ExecutePlan`
this can be implemented in core Datafusion.
- We need a place to store the intermediate plan. This requires unique keys
and handling for keyspace and serialization. So, we need proto updates for this
intermediate logical plan. We can utilize `ObjectStore.put()` in datafusion, or
using *`StateBackendClient`* in Ballista.
- We need some functionality for intermediate plan to actual plan. This can
be handled in core Datafusion, and Ballista scheduler.
- Also, I agree with @alamb to handle `ExecutePlan` outside of the
`DefaultPhysicalPlanner`.
--
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]
