iajoiner opened a new issue, #3014: URL: https://github.com/apache/arrow-datafusion/issues/3014
**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*) We would like to implement new `ExecutionPlan`s and `PhysicalExpr`s that are very similar to existing ones in DataFusion but with some side effects. This requires revising `ExecutionPlan::execute()` and `PhysicalExpr::evaluate()` methods. The problem we have is that we end up re-evaluating and re-executing a lot just for our additional side effects to happen. **Describe the solution you'd like** A clear and concise description of what you want to happen. We need single step versions of ExecutionPlan::execute() and PhysicalExpr::evaluate() methods with the execution/evaluation results of children of a node given as parameters. **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]
