You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2021/04/03 01:59:00 UTC

[jira] [Updated] (BEAM-8552) Spark runner should not used STOPPED state as a terminal state

     [ https://issues.apache.org/jira/browse/BEAM-8552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kenneth Knowles updated BEAM-8552:
----------------------------------
    Status: Open  (was: Triage Needed)

> 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)