Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/511#issuecomment-41356635
@mateiz good point. I agree with you long-term this decision should be up
to the optimizer. However, in this case I think the right thing is probably to
create a section of the sql config called `hints`. We don't promise to obey or
support hints long term, but they can be used for immediate optimizations. This
seems like the typical DB way to offset the cases where the optimization is
currently poor.
---
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.
---
