[jira] [Commented] (SPARK-33139) protect setActiveSession and clearActiveSession

["Apache Spark (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SPARK-33139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214366#comment-17214366 ] 

Apache Spark commented on SPARK-33139:
--------------------------------------

User 'leanken' has created a pull request for this issue:
https://github.com/apache/spark/pull/30042

> protect setActiveSession and clearActiveSession
> -----------------------------------------------
>
>                 Key: SPARK-33139
>                 URL: https://issues.apache.org/jira/browse/SPARK-33139
>             Project: Spark
>          Issue Type: Sub-task
>          Components: SQL
>    Affects Versions: 3.1.0
>            Reporter: Leanken.Lin
>            Priority: Major
>
> This PR is a sub-task of [SPARK-33138](https://issues.apache.org/jira/browse/SPARK-33138). In order to make SQLConf.get reliable and stable, we need to make sure user can't pollute the SQLConf and SparkSession Context via calling setActiveSession and clearActiveSession.
> Change of the PR:
> * add legacy config spark.sql.legacy.allowModifyActiveSession to fallback to old behavior if user do need to call these two API.
> * by default, if user call these two API, it will throw exception
> * add extra two internal and private API setActiveSessionInternal and clearActiveSessionInternal for current internal usage
> * change all internal reference to new internal API exception for SQLContext.setActive and SQLContext.clearActive



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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