[jira] [Resolved] (SPARK-26060) Track SparkConf entries and make SET command reject such entries.

["Wenchen Fan (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SPARK-26060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wenchen Fan resolved SPARK-26060.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 3.0.0

Issue resolved by pull request 23031
[https://github.com/apache/spark/pull/23031]

> Track SparkConf entries and make SET command reject such entries.
> -----------------------------------------------------------------
>
>                 Key: SPARK-26060
>                 URL: https://issues.apache.org/jira/browse/SPARK-26060
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core, SQL
>    Affects Versions: 2.4.0
>            Reporter: Takuya Ueshin
>            Assignee: Takuya Ueshin
>            Priority: Major
>             Fix For: 3.0.0
>
>
> Currently the {{SET}} command works without any warnings even if the specified key is for {{SparkConf}} entries and it has no effect because the command does not update {{SparkConf}}, but the behavior might confuse users. We should track {{SparkConf}} entries and make the command reject for such entries.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org