You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2018/12/05 00:45:00 UTC

[jira] [Commented] (SPARK-24243) Expose exceptions from InProcessAppHandle

    [ https://issues.apache.org/jira/browse/SPARK-24243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16709448#comment-16709448 ] 

Apache Spark commented on SPARK-24243:
--------------------------------------

User 'vanzin' has created a pull request for this issue:
https://github.com/apache/spark/pull/23221

> Expose exceptions from InProcessAppHandle
> -----------------------------------------
>
>                 Key: SPARK-24243
>                 URL: https://issues.apache.org/jira/browse/SPARK-24243
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Submit
>    Affects Versions: 2.3.0
>            Reporter: Sahil Takiar
>            Priority: Major
>
> {{InProcessAppHandle}} runs {{SparkSubmit}} in a dedicated thread, any exceptions thrown are logged and then the state is set to {{FAILED}}. It would be nice to expose the {{Throwable}} object  to the application rather than logging it and dropping it. Applications may want to manipulate the underlying {{Throwable}} / control its logging at a finer granularity. For example, the app might want to call {{Throwables.getRootCause(throwable).getMessage()}} and expose the message to the app users.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org