You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2017/11/15 22:31:00 UTC
[jira] [Commented] (SPARK-22533) SparkConfigProvider does not
handle deprecated config keys
[ https://issues.apache.org/jira/browse/SPARK-22533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254346#comment-16254346 ]
Apache Spark commented on SPARK-22533:
--------------------------------------
User 'vanzin' has created a pull request for this issue:
https://github.com/apache/spark/pull/19760
> SparkConfigProvider does not handle deprecated config keys
> ----------------------------------------------------------
>
> Key: SPARK-22533
> URL: https://issues.apache.org/jira/browse/SPARK-22533
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 2.2.0
> Reporter: Marcelo Vanzin
> Priority: Minor
>
> Noticed that when you read a config using a {{ConfigBuilder}}-created constant using {{SparkConf.get}}, that does not respect the deprecated keys declared in {{SparkConf.configsWithAlternatives}}.
> For example, adding this test to {{SparkConfSuite}} generates a failure:
> {code}
> conf.set("spark.history.fs.cleaner.interval.seconds", "42")
> assert(conf.get(MAX_LOG_AGE_S) === 42L)
> {code}
> While here it would also be nice to handle this TODO from {{SparkConf.configsWithAlternatives}}:
> {noformat}
> * TODO: consolidate it with `ConfigBuilder.withAlternative`.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org