[ https://issues.apache.org/jira/browse/SPARK-5770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14321269#comment-14321269 ]
Patrick Wendell commented on SPARK-5770: ---------------------------------------- If the request is to support hot reloading of classes in a live JVM (can't tell if it is), it seems fairly dangerous to do that. I'm not sure how that works if you have live objects of a specific class and then the class definition changes under them. Anyways, as Sean and Marcelo pointed out, it would be helpful to hear what the intended use case is! > 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