spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Wendell (JIRA)" <>
Subject [jira] [Updated] (SPARK-1480) Chose classloader consistently inside of Spark codebase
Date Sun, 13 Apr 2014 03:51:14 GMT


Patrick Wendell updated SPARK-1480:

    Priority: Blocker  (was: Major)

> Chose classloader consistently inside of Spark codebase
> -------------------------------------------------------
>                 Key: SPARK-1480
>                 URL:
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>            Reporter: Patrick Wendell
>            Assignee: Patrick Wendell
>            Priority: Blocker
>             Fix For: 1.1.0
> The Spark codebase is not always consistent on which class loader it uses when classlaoders
are explicitly passed to things like serializers.
> In most cases what we want is the following behavior:
> 1. If there is a context classloader on the thread, use that.
> 2. Otherwise use the classloader that loaded Spark.
> We should just have a utility function for this and call that function whenever we need
to get a classloader.
> Note that SPARK-1403 is a workaround for this exact problem (it sets the context class
loader because downstream code assumes it is set). Once this gets fixed in a more general
way SPARK-1403 can be reverted.

This message was sent by Atlassian JIRA

View raw message