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/05/21 04:25:32 UTC
[jira] [Updated] (SPARK-17319) Move addJar from HiveSessionState to
HiveSharedState
[ https://issues.apache.org/jira/browse/SPARK-17319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hyukjin Kwon updated SPARK-17319:
---------------------------------
Labels: bulk-closed (was: )
> Move addJar from HiveSessionState to HiveSharedState
> ----------------------------------------------------
>
> Key: SPARK-17319
> URL: https://issues.apache.org/jira/browse/SPARK-17319
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 2.1.0
> Reporter: Xiao Li
> Priority: Major
> Labels: bulk-closed
>
> aThe added jar is shared by all the sessions, because SparkContext does not support sessions. Thus, it makes more sense to move {{addJar}} from `HiveSessionState` to `HiveSharedState`
> This is also another step to remove Hive client usage in `HiveSessionState`.
> Different sessions are sharing the same class loader, and thus, `metadataHive.addJar(path)` basically loads the JARs for all the sessions. Thus, no impact is made if we move `addJar` from `HiveSessionState` to `HiveExternalCatalog`.
--
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