[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=16709450#comment-16709450
]
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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
[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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
[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=16553155#comment-16553155
]
Apache Spark commented on SPARK-24243:
--
User 'sahilTakiar' has created a pull request for this issue:
https://github.com/apache/spark/pull/21849
> 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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
[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=16470797#comment-16470797
]
Marcelo Vanzin commented on SPARK-24243:
Sure. As long as the child process handle returns something meaningful.
> 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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
[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=16470339#comment-16470339
]
Sahil Takiar commented on SPARK-24243:
--
[~vanzin] would adding something like this be possible? Perhaps we can add a
{{getThrowable}} method to {{SparkAppHandle}}?
> 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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
