[
https://issues.apache.org/jira/browse/BEAM-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993159#comment-15993159
]
ASF GitHub Bot commented on BEAM-1641:
--------------------------------------
GitHub user kennknowles opened a pull request:
https://github.com/apache/beam/pull/2826
[BEAM-1641] Use processing time for synchronized processing time in Flink
runner
Be sure to do all of the following to help us incorporate your contribution
quickly and easily:
- [x] Make sure the PR title is formatted like:
`[BEAM-<Jira issue #>] Description of pull request`
- [x] Make sure tests pass via `mvn clean verify`. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
- [x] Replace `<Jira issue #>` in the title with the actual Jira issue
number, if there is one.
- [x] If this contribution is large, please file an Apache
[Individual Contributor License
Agreement](https://www.apache.org/licenses/icla.pdf).
---
There are some esoteric expectations that this might violate, like exactly
one hourly downstream output aligned to an hour, versus a cfewuple, but we
should rephrase docs to remove those expectations IMO.
R: @aljoscha @JingsongLi
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kennknowles/beam Flink-sync-proc
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam/pull/2826.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2826
----
commit 05722accd3da1a92af9f73e85c7ae78742cd9db1
Author: Kenneth Knowles <[email protected]>
Date: 2017-05-02T16:03:03Z
Use processing time for synchronized processing time in Flink runner
----
> 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: Kenneth Knowles
> Priority: Blocker
>
> 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)
