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

Posted to issues@beam.apache.org by "Valentyn Tymofieiev (Jira)" <ji...@apache.org> on 2019/09/05 21:25:00 UTC

[jira] [Resolved] (BEAM-7839) Distinguish unknown and unrecognized states in Dataflow runner.

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

Valentyn Tymofieiev resolved BEAM-7839.
---------------------------------------
    Fix Version/s: 2.16.0
         Assignee: Valentyn Tymofieiev
       Resolution: Fixed

> Distinguish unknown and unrecognized states in Dataflow runner.
> ---------------------------------------------------------------
>
>                 Key: BEAM-7839
>                 URL: https://issues.apache.org/jira/browse/BEAM-7839
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-dataflow
>            Reporter: Valentyn Tymofieiev
>            Assignee: Valentyn Tymofieiev
>            Priority: Major
>             Fix For: 2.16.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> In BEAM-7766 [~kenn] mentioned that when reasoning about pipeline state, Dataflow runner should distinguish between an unknown (to the service) pipeline state state  and unrecognized by the SDK pipeline state.  An unrecognized state may happen when service API introduces a new state that older versions of the  SDK will not know about. Filing this issue to track introducing a distinction.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)