[
https://issues.apache.org/jira/browse/SPARK-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16369112#comment-16369112
]
Shay Elbaz commented on SPARK-5377:
-----------------------------------
+1
This seems like a very useful improvement and will save us many current
workarounds.
Any specific reason for why was this closed?
> Dynamically add jar into Spark Driver's classpath.
> --------------------------------------------------
>
> Key: SPARK-5377
> URL: https://issues.apache.org/jira/browse/SPARK-5377
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Affects Versions: 1.2.0
> Reporter: Chengxiang Li
> Priority: Major
>
> Spark support dynamically add jar to executor classpath through
> SparkContext::addJar(), while it does not support dynamically add jar into
> driver classpath. In most case(if not all the case), user dynamically add jar
> with SparkContext::addJar() because some classes from the jar would be
> referred in upcoming Spark job, which means the classes need to be loaded in
> Spark driver side either,e.g during serialization. I think it make sense to
> add an API to add jar into driver classpath, or just make it available in
> SparkContext::addJar(). HIVE-9410 is a real case from Hive on Spark.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
