[
https://issues.apache.org/jira/browse/BEAM-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993520#comment-15993520
]
Kenneth Knowles commented on BEAM-1641:
---------------------------------------
This is now implemented as processing time; leaving open this as a low priority
ticket in case Flink adds the capabilities needed to make it easy. But in the
meantime we can improve Beam in this area.
> Implement real 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: Kenneth Knowles
> Priority: Minor
>
> 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)
