[
https://issues.apache.org/jira/browse/BEAM-14265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17534312#comment-17534312
]
Jan Lukavský commented on BEAM-14265:
-------------------------------------
Unfortunately there is no way of telling if a particular Pipeline uses
processing-time timers with output timestamp, hence rejecting a Pipeline at
Pipeline submission time seems impossible (only option would be to reject all
processing-time timers, but that would be a regression). I think the fix is not
that complicated (most complicated part is probably a correct construction of a
{{@ValidatesRunner}} test), I'll try to look into that before next release.
Marking this as fix version of 2.40.0.
> 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)
