GitHub user andrewor14 opened a pull request:
https://github.com/apache/spark/pull/4799
[SPARK-6048] SparkConf should not translate deprecated configs on set
There are multiple issues with translating on set. I will highlight the
most serious one here (the rest are on the JIRA).
If the user has both the deprecated and the latest version of the same
config set, then the value picked up by SparkConf will be arbitrary. This is
because in the `SparkConf` constructor we call `conf.set` on each property in
`sys.props` in an order arbitrarily defined by Java. As a result, the value of
the more recent config may be overridden by that of the deprecated one.
Instead, we should always use the value of the most recent config.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/andrewor14/spark conf-set-translate
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/4799.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 #4799
----
commit 94b4dfaadc62182df45185e4c2d7bc7da6c1ee45
Author: Andrew Or <and...@databricks.com>
Date: 2015-02-27T00:57:20Z
Translate on get, not set
----
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
