[GitHub] [arrow-datafusion] Dandandan commented on issue #4003: Representing statistics in logical or physical plans (or in both of them)

[GitBox <gi...@apache.org>]

Dandandan commented on issue #4003:
URL: https://github.com/apache/arrow-datafusion/issues/4003#issuecomment-1298119788

   Another benefit of keeping the CBOs at physical level is that the costs might be also different for different ways. E.g. hash join and sort merge join do have different costs associated with them. For a hash join swapping the order of the build and probe side has a big impact, but a sort merge join (or other types of join) might not benefit from this change (or at least in very different ways).
   
   If we would move the optimization to be on logical plans, we would need a way to expose this to the logical plan too.


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