Github user sryza commented on the pull request:
https://github.com/apache/spark/pull/3505#issuecomment-66564746
+1 to different method names vs. immutable confs. To throw in my two
cents, I do think it's worthwhile to add this at a Spark core level. It
probably doesn't make sense to add logic to Spark core's join transformation to
figure out the optimal join strategy. But exposing different join
transformations that implement different strategies is useful in a couple cases
* Advanced users that deeply understand their access patterns and can
decide which of these to use directly.
* Other DSLs on top of Spark core like Pig, Hive, and Scalding.
---
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]
