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/11/08 21:31:45 UTC

[GitHub] [arrow-datafusion] alamb commented on issue #4139: JoinSelection Rule to choose physical join implementation: HashJoin(Partitioned or CollectLeft) or SortMergeJoin base on Stats

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

   I agree with @Dandandan  that doing some benchmarking on sort merge join is likely a good idea. I don't think we have much at the moment as it is never used.
   
   What I think would be an ideal solution, though maybe harder to implement, is to *NOT* decide between has or sort merge join at plan time, but to decide at runtime
   
   So that would involve starting out using HashJoin but if the hash table spilled (or exceeded some size threshold) sort/spill it and then switch to sort-merge-join
   
   


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