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 2021/05/24 17:39:07 UTC

[GitHub] [arrow-datafusion] alamb commented on issue #412: DefaultPhysicalPlanner Generates Invalid Physical Plans

alamb commented on issue #412:
URL: https://github.com/apache/arrow-datafusion/issues/412#issuecomment-847217157


   Clearly separating the logic / transformations needed for the plan to produce the correct answers and the transformations that aim to make it go faster (e.g. optimizations) makes a lot of sense to me.
   
   One approach that seems reasonable to me would be to take the pass in https://github.com/apache/arrow-datafusion/blob/master/datafusion/src/physical_optimizer/merge_exec.rs and call it directly from the `DefaultPhysicalPlanner` always. Depending on where else it is used, we may even consider not exposing it as a `PhysicalOptimizerRule`


-- 
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.

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