thinkharderdev opened a new issue, #8: URL: https://github.com/apache/arrow-ballista/issues/8
**Is your feature request related to a problem or challenge? Please describe what you are trying to do.** A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] (This section helps Arrow developers understand the context and *why* for this feature, in addition to the *what*) Currently, we are working with DataFusion/Ballista as a query execution engine. One of the primary selling points for DataFusion is extensibility but it is not currently possible to use the many extension points in DataFusion with Ballista. This is primarily due to the constraints of serializing all logical and physical plans as Protobuf messages. Ideally we would like to use Ballista to execute: * Scans using custom object stores * User Defined logical plan extensions * User defined physical plan extensions * User defined scalar and aggregation functions **Describe the solution you'd like** A clear and concise description of what you want to happen. There are two things ideally: 1. We would like to decouple the core Ballista functionality from the serializable representations of plans so that the serde layer can become pluggable/extensible. 2. Serde should be aware of a user-defined `ExecutionContext` so we can leverage optimizers, extension planners, and udf/udaf **Describe alternatives you've considered** A clear and concise description of any alternative solutions or features you've considered. There currently is no workaround for this but we have been prototyping possible solutions which we'd be interested in upstreaming. **Additional context** Add any other context or screenshots about the feature request here. -- 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]
