You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by "Pei He (JIRA)" <ji...@apache.org> on 2017/06/02 02:55:04 UTC

[jira] [Created] (BEAM-2402) Support AfterPane.elementGapAtMost() trigger and its combination with elementCountAtLeast()

Pei He created BEAM-2402:
----------------------------

             Summary: Support AfterPane.elementGapAtMost() trigger and its combination with elementCountAtLeast()
                 Key: BEAM-2402
                 URL: https://issues.apache.org/jira/browse/BEAM-2402
             Project: Beam
          Issue Type: New Feature
          Components: sdk-java-core
            Reporter: Pei He
            Assignee: Davor Bonaci


We need a timestamp-driven trigger to use as a cheaper (or more efficient) version of the ProcessingTime trigger.

The problem of using ProcessingTime trigger is that current runners' supports are not very efficient, and couldn't work for pipelines that have lots of keys (for example, flink runner will scan timers for all keys when watermark advance).

We have used AfterPane.elementGapAtMost() trigger in our production, and want to merge it back. And, we believe it could be the solution for people who have the similar issue.

Implementation for reference:
https://github.com/apache/beam/compare/master...peihe:custom-after-pane?expand=1



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)