Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/956#issuecomment-45419468
I agree that it would be silly to expose only the setters but not the other
methods. However, the extra syntactic overhead of typing `.sqlConf.` seems
unnecessary since I don't think a `set` method would on `SQLContext` would ever
do something other than modify configuration.
There is maybe some code cleanliness that comes from not adding all this
logic to SQLContext.scala. However we could probably achieve this by making
configuration a trait that is mixed in.
---
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.
---
