GitHub user tomwhite opened a pull request:

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

    [SPARK-8625] [Core] Propagate user exceptions in tasks back to driver

    This allows clients to retrieve the original exception from the
    cause field of the SparkException that is thrown by the driver.
    If the original exception is not in fact Serializable then it will
    not be returned, but the message and stacktrace will be. (All Java
    Throwables implement the Serializable interface, but this is no
    guarantee that a particular implementation can actually be
    serialized.)

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

    $ git pull https://github.com/tomwhite/spark propagate-user-exceptions

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

    https://github.com/apache/spark/pull/7014.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 #7014
    
----
commit fc484b9fdf4d0229d45d3704e07424586dcf5aa3
Author: Tom White <[email protected]>
Date:   2015-06-24T16:29:14Z

    Return runtime exceptions in tasks back to driver.
    
    This allows clients to retrieve the original exception from the
    cause field of the SparkException that is thrown by the driver.
    If the original exception is not in fact Serializable then it will
    not be returned, but the message and stacktrace will be. (All Java
    Throwables implement the Serializable interface, but this is no
    guarantee that a particular implementation can actually be
    serialized.)

----


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