You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2017/02/10 01:25:41 UTC

[jira] [Assigned] (SPARK-19540) Add ability to clone SparkSession wherein cloned session has a reference to SharedState and an identical copy of the SessionState

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

Apache Spark reassigned SPARK-19540:
------------------------------------

    Assignee:     (was: Apache Spark)

> Add ability to clone SparkSession wherein cloned session has a reference to SharedState and an identical copy of the SessionState
> ---------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SPARK-19540
>                 URL: https://issues.apache.org/jira/browse/SPARK-19540
>             Project: Spark
>          Issue Type: Story
>          Components: SQL
>    Affects Versions: 2.1.1
>            Reporter: Kunal Khamar
>
> Forking a newSession() from SparkSession currently makes a new SparkSession that does not retain SessionState (i.e. temporary tables, SQL config, registered functions etc.) This change adds a method cloneSession() which creates a new SparkSession with a copy of the parent's SessionState.
> Subsequent changes to base session are not propagated to cloned session, clone is independent after creation.
> If the base is changed after clone has been created, say user registers new UDF, then the new UDF will not be available inside the clone. Same goes for configs and temp tables.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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