[
https://issues.apache.org/jira/browse/BEAM-14265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525916#comment-17525916
]
Steve Niemitz commented on BEAM-14265:
--------------------------------------
The output timestamp is ignored yes. I was hesitant to make this a P1 because
it seems like it's always been like this, although new validation added to
outputs from timestamps made it more noticeable that the timestamp was
incorrect.
> Flink should hold the watermark at the output timestamp for processing time
> timers
> ----------------------------------------------------------------------------------
>
> Key: BEAM-14265
> URL: https://issues.apache.org/jira/browse/BEAM-14265
> Project: Beam
> Issue Type: Bug
> Components: runner-flink
> Reporter: Steve Niemitz
> Priority: P1
>
> Currently the Flink runner doesn't support output timestamps on processing
> time timers, and instead uses the current output watermark when the timer
> fires.
> We should update the runner to correctly set a watermark hold at the output
> timestamp and use it when firing the timer.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
