[
https://issues.apache.org/jira/browse/BEAM-7839?focusedWorklogId=290314&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-290314
]
ASF GitHub Bot logged work on BEAM-7839:
----------------------------------------
Author: ASF GitHub Bot
Created on: 07/Aug/19 09:01
Start Date: 07/Aug/19 09:01
Worklog Time Spent: 10m
Work Description: tvalentyn commented on issue #9132: [BEAM-7839] Default
to UNRECOGNIZED state when a state cannot be accurately interpreted by the SDK.
URL: https://github.com/apache/beam/pull/9132#issuecomment-519009560
R: @kennknowles (once you are back).
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 290314)
Time Spent: 0.5h (was: 20m)
> 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
> Priority: Major
> Time Spent: 0.5h
> 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
(v7.6.14#76016)
