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

Posted to issues@beam.apache.org by "Chad Dombrova (Jira)" <ji...@apache.org> on 2019/11/04 17:54:00 UTC

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

Chad Dombrova created BEAM-8552:
-----------------------------------

             Summary: 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


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)