[SPARK-6046] Provide an easier way for developers to handle deprecated configs

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.3.0
• Fix Version/s: 1.4.0
• Component/s: Spark Core
• Target Version/s: 1.4.0
• Assignee: Marcelo Masiero Vanzin
• Reporter: Andrew Or
• Created: 26/Feb/15 21:26
• Updated: 17/Apr/15 17:09
• Resolved: 17/Apr/15 10:06

Description

Right now we have code that looks like this:
https://github.com/apache/spark/blob/8942b522d8a3269a2a357e3a274ed4b3e66ebdde/core/src/main/scala/org/apache/spark/deploy/history/FsHistoryProvider.scala#L52

where a random class calls `SparkConf.translateConfKey` to warn the user against a deprecated configs. We should refactor this slightly so we can make `translateConfKey` private instead of calling it from everywhere.

Issue Links

• links to: [Github] Pull Request #4797 (andrewor14)
• links to: [Github] Pull Request #5514 (vanzin)