Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/10205#issuecomment-164026937
I am in favor of the high level approach. The biggest problem right now is
several things are duplicated everywhere around the code:
- config key name
- config default value
- deprecation logic (maybe we fixed this already)
I'm thinking we can just create a `conf.scala` file in each module that
introduces configs, and just do something like
```
import org.apache.spark.conf._
import org.apache.spark.sql.conf._
```
---
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]
