[ https://issues.apache.org/jira/browse/BEAM-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15902802#comment-15902802 ]
Aljoscha Krettek commented on BEAM-1641: ---------------------------------------- Wow, that's a tough one. I think we might first have to introduce such a concept in Flink if we want to use it from Beam. > 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 > > 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)