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

Kenneth Knowles commented on BEAM-8983:
---------------------------------------

This issue is assigned but has not received an update in 30 days so it has been 
labeled "stale-assigned". If you are still working on the issue, please give an 
update and remove the label. If you are no longer working on the issue, please 
unassign so someone else may work on it. In 7 days the issue will be 
automatically unassigned.

> Spark uber jar job server: query exceptions from master
> -------------------------------------------------------
>
>                 Key: BEAM-8983
>                 URL: https://issues.apache.org/jira/browse/BEAM-8983
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-spark
>            Reporter: Kyle Weaver
>            Assignee: Kyle Weaver
>            Priority: P2
>              Labels: portability-spark, stale-assigned
>
> As far as I know, the Spark REST API does not return exceptions from the 
> cluster after a jar is actually run. While these exceptions can be viewed in 
> Spark's web UI, ideally they would also be visible in Beam's output.
> To do this, we will need to find a REST endpoint that does return those 
> exceptions, and then map the submissionId to its corresponding job id.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to