yahoNanJing opened a new issue, #3651:
URL: https://github.com/apache/arrow-datafusion/issues/3651
**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*) -->
As #2175 mentioned, if we still keep *ExecutionPlan* as a trait, its related
trait object usage will cause many limitations, like not feasible to return
Self, inconvenience pattern matching, etc.
**Describe the solution you'd like**
<!-- A clear and concise description of what you want to happen. -->
It's better to change the *ExecutionPlan* from trait to enum similar as
*LogicalPlan*. For the extension of execution plan, we can introduce a trait
for that to provide some extent flexibility, like
```
enum ExecutionPlan {
...
Extension {
extension: Arc<dyn ExecutionPlanExtension>,
}
...
```
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features
you've considered.
**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]
