[
https://issues.apache.org/jira/browse/BEAM-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988363#comment-15988363
]
Jingsong Lee commented on BEAM-1641:
------------------------------------
I think it is difficult to achieve, it requires Flink-runtime
{{StatusWatermarkValve}} also manage synchronized processing time.(maybe in
Flink 1.4 or latter) It's a tough one indeed. I have no idea about using some
special punctuation(s) to trigger too. I think it can be deferred. What do you
think? [~aljoscha]
> Support synchronized processing time in Flink runner
> ----------------------------------------------------
>
> Key: BEAM-1641
> URL: https://issues.apache.org/jira/browse/BEAM-1641
> Project: Beam
> Issue Type: Bug
> Components: runner-flink
> Reporter: Kenneth Knowles
> Assignee: Aljoscha Krettek
> Priority: Blocker
> Fix For: First stable release
>
>
> The "continuation trigger" for a processing time trigger is a synchronized
> processing time trigger. Today, this throws an exception in the FlinkRunner.
> The supports the following:
> - GBK1
> - GBK2
> When GBK1 fires due to processing time past the first element in the pane and
> that element arrives at GBK2, it will wait until all the other upstream keys
> have also processed and emitted corresponding data.
> Sorry for the terseness of explanation - writing quickly so I don't forget.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
