spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kunal Khamar (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SPARK-19540) Add ability to clone SparkSession wherein cloned session has a reference to SharedState and an identical copy of the SessionState
Date Fri, 10 Feb 2017 21:16:41 GMT

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

Kunal Khamar updated SPARK-19540:
---------------------------------
    Affects Version/s:     (was: 2.1.1)
                       2.2.0

> 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: Improvement
>          Components: SQL
>    Affects Versions: 2.2.0
>            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


Mime
View raw message