LiaCastaneda commented on issue #18296: URL: https://github.com/apache/datafusion/issues/18296#issuecomment-3451438824
> ExecutionPlan implementations can return all the PhysicalExpr to which they are pointing to, and users can recursively walk this expressions looking for references to Arc<DynamicFilterPhysicalExpr>s that they can then manipulate with whatever DynamicFilterPhysicalExpr decides to expose. This is for the consumer right? I think its very similar to what we currently do in our custom `ExecutionPlan`s: we store a vec with the physicalExprs we get [here](https://github.com/apache/datafusion/blob/1feb80f1648e8b58c002971ec66d72386d72877d/datafusion/physical-plan/src/execution_plan.rs#L643) in the custom node struct, then it would be very useful for single node too since we are lacking a "wait for the dynamic filter to update" method Not sure if it would be recursively though, it would be enough to iterate i think? I would expect a vec like [PhysicalExpr, PhysicalExpr, DynamicFilter] -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
