[
https://issues.apache.org/jira/browse/SPARK-30223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16994061#comment-16994061
]
angerszhu edited comment on SPARK-30223 at 12/12/19 1:49 AM:
-------------------------------------------------------------
[~cloud_fan]
Add
```
SparkSession.setActiveSession(sqlContext.sparkSession)
```
in each Metadata Operation?
Maybe we should sort out the use of `SQLConf.get()` like
https://github.com/apache/spark/pull/26187
was (Author: angerszhuuu):
[~cloud_fan]
Add
```
SparkSession.setActiveSession(sqlContext.sparkSession)
```
in each Metadata Operation?
> queries in thrift server may read wrong SQL configs
> ---------------------------------------------------
>
> Key: SPARK-30223
> URL: https://issues.apache.org/jira/browse/SPARK-30223
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 3.0.0
> Reporter: Wenchen Fan
> Priority: Major
>
> The Spark thrift server creates many SparkSessions to serve requests, and the
> thrift server serves requests using a single thread. One thread can only have
> one active SparkSession, so SQLCong.get can't get the proper conf from the
> session that runs the query.
> Whenever we issue an action on a SparkSession, we should set this session as
> active session, e.g. `SparkSession.sql`.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
