[
https://issues.apache.org/jira/browse/BEAM-10015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17111554#comment-17111554
]
Kyle Weaver commented on BEAM-10015:
------------------------------------
Sorry I missed this. It was pointed out on the mailing list that this issue is
not fixed in 2.21.0. I invite someone who has more context on the bug to
clarify its severity. I'm also curious whether or not this was a regression
from previous Beam releases.
> output timestamp not properly propagated through the Dataflow runner
> --------------------------------------------------------------------
>
> Key: BEAM-10015
> URL: https://issues.apache.org/jira/browse/BEAM-10015
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow
> Reporter: Reuven Lax
> Priority: P1
> Fix For: 2.21.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Dataflow runner does not propagate the output timestamp into timer firing,
> resulting in incorrect default timestamps when outputting from a processTimer.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
