[
https://issues.apache.org/jira/browse/BEAM-8552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17314148#comment-17314148
]
Kenneth Knowles commented on BEAM-8552:
---------------------------------------
I think the result enums were basically carried over from the early days of
Dataflow without meaningful design as to being runner-agnostic and extensible.
Is this still an issue? Does the runner map Spark job statuses to inappropriate
enums?
> Spark runner should not used STOPPED state as a terminal state
> --------------------------------------------------------------
>
> Key: BEAM-8552
> URL: https://issues.apache.org/jira/browse/BEAM-8552
> Project: Beam
> Issue Type: Bug
> Components: runner-spark
> Reporter: Chad Dombrova
> Priority: P3
>
> Over at BEAM-8539 we're trying to iron out the definitions of the job state
> enums. One thing that is clear is that STOPPED is not supposed to be a
> terminal state, though since it was poorly documented it slipped in a few
> places.
> There are two places in the {{SparkPipelineResult}} where STOPPED seems to be
> used as a terminal event. These should either be DONE, FAILED, or CANCELLED.
> Here's one example:
> [https://github.com/apache/beam/blob/master/runners/spark/src/main/java/org/apache/beam/runners/spark/SparkPipelineResult.java#L133]
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
