[ https://issues.apache.org/jira/browse/SPARK-17319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiao Li updated SPARK-17319:
----------------------------
Description:
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`.
was:
This is 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`.
> 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
>
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org
|