Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1127#issuecomment-54251469
Hi @YanjieGao, thank for working on this! I think it would be great to
support this optimization. However, I think the hardest part here is going to
be figuring how to hook this into the planner such that it is chosen when the
data requires it, and otherwise we use the standard join algorithms. Since I
think that is going to a pretty large task, perhaps it would be best to close
this issue for now and revisit it when we have a full design for how choose
join operators.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
