You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Wenchen Fan (Jira)" <ji...@apache.org> on 2022/03/31 11:14:00 UTC
[jira] [Resolved] (SPARK-38713) Change spark.sessionstate.conf.getConf/setConf operation to spark.conf.get/set
[ https://issues.apache.org/jira/browse/SPARK-38713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wenchen Fan resolved SPARK-38713.
---------------------------------
Fix Version/s: 3.4.0
Assignee: Jackey Lee
Resolution: Fixed
> Change spark.sessionstate.conf.getConf/setConf operation to spark.conf.get/set
> ------------------------------------------------------------------------------
>
> Key: SPARK-38713
> URL: https://issues.apache.org/jira/browse/SPARK-38713
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 3.4.0
> Reporter: Jackey Lee
> Assignee: Jackey Lee
> Priority: Major
> Fix For: 3.4.0
>
>
> In the sql module, we provide {{SparkSession.conf}} as a unified entry for {{{}SQLConf.set/get{}}}, which can prevent users or logic from modifying StaticSQLConf and Spark configs. However, I found {{SparkSession.sessionstate.conf}} is used in some code to getConf or setConf, which can skip the check of {{{}RuntimeConfig{}}}.
> In this PR, we want to unify the behavior of {{SQLConf.getConf/setConf}} to {{{}SparkSession.conf{}}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org