You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2015/04/17 12:06:59 UTC
[jira] [Resolved] (SPARK-6046) Provide an easier way for developers
to handle deprecated configs
[ https://issues.apache.org/jira/browse/SPARK-6046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Owen resolved SPARK-6046.
------------------------------
Resolution: Fixed
Fix Version/s: 1.4.0
Issue resolved by pull request 5514
[https://github.com/apache/spark/pull/5514]
> Provide an easier way for developers to handle deprecated configs
> -----------------------------------------------------------------
>
> Key: SPARK-6046
> URL: https://issues.apache.org/jira/browse/SPARK-6046
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 1.3.0
> Reporter: Andrew Or
> Assignee: Andrew Or
> Priority: Minor
> Fix For: 1.4.0
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org