GitHub user gatorsmile opened a pull request:
https://github.com/apache/spark/pull/13247
[SPARK-15470] [SQL] Unify the Configuration Interface in SQLContext
#### What changes were proposed in this pull request?
We introduced `RuntimeConfig` in `SQLContext` in the PR
https://github.com/apache/spark/pull/12669. Now, `SQLContext` has both `conf`
and `runtimeConf`. `SQLContext` is being replaced by `SparkSession`. Like
`SparkSession`, we should not have two configuration interfaces. That means, we
should not expose `conf` to external users.
This PR contains three major parts:
1. removed `conf` from `SQLContext`.
2. added the missing functions into `RuntimeConfig`, including two `set`
functions and one `clear` function.
3. fixed the test cases in `SparkSessionBuilderSuite.scala`. Without this
fix, we are unable to individually run the test cases. All the test cases
require `initialSession`.
@rxin @andrewor14 @yhuai @cloud-fan Do you think this PR is valid? Thanks!
#### How was this patch tested?
Existing test cases cover it.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gatorsmile/spark configNew
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/13247.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #13247
----
commit f5708f52171ef5ce04eb4358d101d55862cc2294
Author: gatorsmile <[email protected]>
Date: 2016-05-21T21:25:38Z
initial fix.
commit 0808fa13f04a228377be8f1d17d0aa7da4a47aee
Author: gatorsmile <[email protected]>
Date: 2016-05-22T03:29:38Z
update the test suites.
commit f443064bfabb9e1055d75b7ee1b33085d72b1a3f
Author: gatorsmile <[email protected]>
Date: 2016-05-22T04:33:35Z
remove conf from SQLContext
----
---
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]
