[
https://issues.apache.org/jira/browse/BEAM-7766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16888164#comment-16888164
]
Valentyn Tymofieiev commented on BEAM-7766:
-------------------------------------------
Yes, UNKNOWN can be returned by the service as well, however Java SDK behavior
does not distinguish between "unknown to SDK" and "reported unknown by
service" see: [1, 2].
Is there a particular use-case you have in mind where the two states should be
treated differently? In case of Python SDK I believe UNKNOWN is not interpreted
at all by Dataflow Runner, instead the runner interprets other states, for
example whether they are terminal or not, so I don't see such use-case as of
now.
[1]
https://github.com/apache/beam/blob/79348262cd06a84f83e8aa7b963673c575b71316/runners/google-cloud-dataflow-java/src/main/java/org/apache/beam/runners/dataflow/util/MonitoringUtil.java#L222
[2]
https://github.com/apache/beam/blob/c2f0d282337f3ae0196a7717712396a5a41fdde1/runners/google-cloud-dataflow-java/src/main/java/org/apache/beam/runners/dataflow/util/MonitoringUtil.java#L54
> Dataflow runner should default to PiplelineState.UNKNOWN when job state
> received via v1beta3 cannot be recognized.
> ------------------------------------------------------------------------------------------------------------------
>
> Key: BEAM-7766
> URL: https://issues.apache.org/jira/browse/BEAM-7766
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow
> Affects Versions: 2.1.0
> Reporter: Valentyn Tymofieiev
> Assignee: Valentyn Tymofieiev
> Priority: Minor
> Fix For: 2.7.1, 2.15.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
