GitHub user choochootrain opened a pull request:

    https://github.com/apache/spark/pull/9779

    [SPARK-11195][CORE] Use correct classloader for TaskResultGetter

    Make sure we are using the context classloader when deserializing failed 
TaskResults instead of the Spark classloader.
    
    The issue is that `enqueueFailedTask` was using the incorrect classloader 
which results in `ClassNotFoundException`.
    
    Adds a test in TaskResultGetterSuite that compiles a custom exception, 
throws it on the executor, and asserts that Spark handles the TaskResult 
deserialization instead of returning `UnknownReason`.
    
    See #9367 for previous comments
    See SPARK-11195 for a full repro

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/choochootrain/spark spark-11195-master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/9779.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #9779
    
----
commit 93939c3f485cd8af9a544a0458a505042a54084c
Author: Hurshal Patel <[email protected]>
Date:   2015-10-30T01:05:44Z

    [SPARK-11195][CORE] Use correct classloader for TaskResultGetter
    
    Make sure we are using the context classloader when deserializing failed
    TaskResults instead of the Spark classloader.
    
    Adds a test in TaskResultGetterSuite that compiles a custom exception,
    throws it on the executor, and asserts that Spark handles the
    TaskResult deserialization properly.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to