GitHub user vanzin opened a pull request:
https://github.com/apache/spark/pull/19760
[SPARK-22533][core] Handle deprecated names in ConfigEntry.
This change undoes the ConfigEntry changes introduced in SPARK-20887,
while keeping the config deprecation that was added of part of that
change.
Instead, it hooks up the config reader to `SparkConf.getDeprecatedConfig`,
which is better since declaring name changes in `SparkConf` enables
deprecation messages when old config names are used. The `withAlternatives`
approach has limitations in that area since it would not be possible to
handle config constants declared outside of core in that way.
Added a few unit tests to verify the desired behavior.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vanzin/spark SPARK-22533
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/19760.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 #19760
----
commit fcf3fbfc47fbf4ea7290f74e65f324eee68f7aba
Author: Marcelo Vanzin <[email protected]>
Date: 2017-11-15T21:35:05Z
[SPARK-22533][core] Handle deprecated names in ConfigEntry.
This change undoes the ConfigEntry changes introduced in SPARK-20887,
while keeping the config deprecation that was added of part of that
change.
Instead, it hooks up the config reader to `SparkConf.getDeprecatedConfig`,
which is better since declaring name changes in `SparkConf` enables
deprecation messages when old config names are used. The `withAlternatives`
approach has limitations in that area since it would not be possible to
handle config constants declared outside of core in that way.
Added a few unit tests to verify the desired behavior.
----
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
