[
https://issues.apache.org/jira/browse/BEAM-10015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17114517#comment-17114517
]
Kenneth Knowles commented on BEAM-10015:
----------------------------------------
[~reuvenlax] the typical protocol I use is to put Fix Version = 2.22 on this
bug and make a separate Jira for the cherrypick and put Fix Version = 2.21 and
do not resolve until it is on the 2.21 branch so it is sure to be released.
> 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
> Assignee: 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)
