[
https://issues.apache.org/jira/browse/BEAM-14265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528788#comment-17528788
]
Kenneth Knowles commented on BEAM-14265:
----------------------------------------
Yea I think that the short-term action item, and the thing that should have
blocked inclusion of the feature, is a quick check to reject pipelines that use
the feature, for runners that don't yet support it. We need to work out a way
to "reject by default" for new features so that feature authors don't have to
dive into all of their code.
> 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)
