[
https://issues.apache.org/jira/browse/BEAM-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856453#comment-15856453
]
Jingsong Lee commented on BEAM-1393:
------------------------------------
(y)
But there is a problem with the 6 point.
AbstractStreamOperator.processWatermark did two things: advanceTimerWatermark
and emitWatermark.
Now in Beam, advanceTimerWatermark is determined by inputWatermark,
emitWatermark is determined by Min(inputWatermark,
StateInternals.watermarkHold). Their watermarks is not the same.
Even, advancing watermarkHold need fireTimer to clear early namespace.
> Update Flink Runner to Flink 1.2.0
> ----------------------------------
>
> Key: BEAM-1393
> URL: https://issues.apache.org/jira/browse/BEAM-1393
> Project: Beam
> Issue Type: Improvement
> Components: runner-flink
> Reporter: Aljoscha Krettek
> Assignee: Jingsong Lee
>
> When we update to 1.2.0 we can use the new internal Timer API that is
> available to Flink operators: {{InternalTimerService}} and also use broadcast
> state to store side-input data.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
