[jira] [Resolved] (SPARK-11194) Use a single URLClassLoader for jars added through SQL's "ADD JAR" command

["Yin Huai (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SPARK-11194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yin Huai resolved SPARK-11194.
------------------------------
       Resolution: Fixed
    Fix Version/s: 1.6.0

Issue resolved by pull request 9170
[https://github.com/apache/spark/pull/9170]

> Use a single URLClassLoader for jars added through SQL's "ADD JAR" command
> --------------------------------------------------------------------------
>
>                 Key: SPARK-11194
>                 URL: https://issues.apache.org/jira/browse/SPARK-11194
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Yin Huai
>            Assignee: Yin Huai
>             Fix For: 1.6.0
>
>
> Right now, we stack a new URLClassLoader when a user add a jar through SQL's add jar command. This approach can introduce issues caused by the ordering of added jars when a class of a jar depends on another class of another jar.
> For example,
> {code}
> ClassLoader1 for Jar1.jar (A.class)
>    |
>    |----- ClassLoader2 for Jar2.jar (B.class depending on A.class)
> {code}
> In this case, when we lookup class B, we will not be able to find class A because Jar2 is the parent of Jar1.



--
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