Github user marmbrus commented on the pull request:

    https://github.com/apache/spark/pull/1190#issuecomment-47176944
  
    I'm not sure what the point of this change is.  It is only serving to make 
the planner more brittle and tied to the specifics of the current 
implementation of the optimizer.
    
    If the current pattern for hash joins is correct and more general, I think 
we should keep it.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to