[
https://issues.apache.org/jira/browse/SPARK-5770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14320504#comment-14320504
]
Marcelo Vanzin commented on SPARK-5770:
---------------------------------------
bq. but the classloader still load the old one.
Could you clarify what that means? Due to the way class loading works, if you
reference a class that has already been loaded, you won't get the new one, but
the one already loaded. Which is one reason why this "addJar() can overwrite
existing jars" functionality is a little sketchy.
> Use addJar() to upload a new jar file to executor, it can't be added to
> classloader
> -----------------------------------------------------------------------------------
>
> Key: SPARK-5770
> URL: https://issues.apache.org/jira/browse/SPARK-5770
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Reporter: meiyoula
>
> First use addJar() to upload a jar to the executor, then change the jar
> content and upload it again. We can see the jar file in the local has be
> updated, but the classloader still load the old one. The executor log has no
> error or exception to point it.
> I use spark-shell to test it. And set "spark.files.overwrite" is true.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
