[
https://issues.apache.org/jira/browse/SPARK-6630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Owen resolved SPARK-6630.
------------------------------
Resolution: Won't Fix
Idea was good, just probably can't be reconciled with binary compatibility at
this point without significantly more change, so closing. If there's a
particularly expensive computation we want to avoid, we can fix those directly
by checking the property's existence first before computing and setting a new
value.
> SparkConf.setIfMissing should only evaluate the assigned value if indeed
> missing
> --------------------------------------------------------------------------------
>
> Key: SPARK-6630
> URL: https://issues.apache.org/jira/browse/SPARK-6630
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Affects Versions: 1.3.0
> Reporter: Svend Vanderveken
> Priority: Minor
>
> The method setIfMissing() in SparkConf is currently systematically evaluating
> the right hand side of the assignment even if not used. This leads to
> unnecessary computation, like in the case of
> {code}
> conf.setIfMissing("spark.driver.host", Utils.localHostName())
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
