Uploaded image for project: 'Beam'
  1. Beam
  2. BEAM-8552

Spark runner should not used STOPPED state as a terminal state

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Triage Needed
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: runner-spark
    • Labels:
      None

      Description

      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

       

       

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              chadrik Chad Dombrova
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: