You are viewing a plain text version of this content. The canonical link for it is here.

Posted to github@arrow.apache.org by GitBox <gi...@apache.org> on 2022/10/26 16:04:59 UTC

[GitHub] [arrow-datafusion] jackwener commented on pull request #3972: draft: refactor optimizer to avoid every rule must recursive children.

jackwener commented on PR #3972:
URL: https://github.com/apache/arrow-datafusion/pull/3972#issuecomment-1292274816

   > I also implemented similar things to PhysicalExprs. I think we can have a unified Trait.
   > 
   > https://github.com/apache/arrow-datafusion/blob/b705574cbb334fd07aab355437a56aa118e578f9/datafusion/physical-expr/src/physical_expr.rs
   
   Yes, Essentially it's the same thing.
   
   The main difference is that one is a plan tree and the other is an expression book tree


-- 
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: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org