Github user cloud-fan commented on the issue:

    https://github.com/apache/spark/pull/21109
  
    I think range join is a very important feature, but the current 
implementation is not robust enough(no spilling to disk). Have you explored 
other simpler solutions? I vaguely remember that some papers describe a way to 
rewrite range join to equal-join during the logical phase.


---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to