You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (JIRA)" <ji...@apache.org> on 2019/04/01 00:34:00 UTC
[jira] [Resolved] (SPARK-27253) SparkSession clone discards SQLConf
overrides in favor of SparkConf defaults
[ https://issues.apache.org/jira/browse/SPARK-27253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hyukjin Kwon resolved SPARK-27253.
----------------------------------
Resolution: Fixed
Fix Version/s: 3.0.0
Issue resolved by pull request 24189
[https://github.com/apache/spark/pull/24189]
> SparkSession clone discards SQLConf overrides in favor of SparkConf defaults
> ----------------------------------------------------------------------------
>
> Key: SPARK-27253
> URL: https://issues.apache.org/jira/browse/SPARK-27253
> Project: Spark
> Issue Type: Bug
> Components: Structured Streaming
> Affects Versions: 2.4.0
> Reporter: Jose Torres
> Assignee: Chakravarthi
> Priority: Major
> Fix For: 3.0.0
>
>
> SparkSession.cloneSession() is normally supposed to create a child session which inherits all the SQLConf values of its parent session. But when a SQL conf is given a global default through the SparkConf, this does not happen; the child session will receive the SparkConf default rather than its parent's SQLConf override.
>
> This is particularly impactful in structured streaming, as the microbatches run in a cloned child session.
--
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