[
https://issues.apache.org/jira/browse/SPARK-24243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcelo Vanzin resolved SPARK-24243.
------------------------------------
Resolution: Fixed
Fix Version/s: 3.0.0
Issue resolved by pull request 23221
[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
> Assignee: Sahil Takiar
> Priority: Major
> Fix For: 3.0.0
>
>
> {{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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
