You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2022/04/21 17:38:00 UTC

[jira] [Commented] (BEAM-14265) Flink should hold the watermark at the output timestamp for processing time timers

    [ https://issues.apache.org/jira/browse/BEAM-14265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525890#comment-17525890 ] 

Kenneth Knowles commented on BEAM-14265:
----------------------------------------

Does it ignore the value (a data correctness bug) or does it reject the pipeline or fail at runtime?

> 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: P2
>
> 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)