beam-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Beam JIRA Bot (Jira)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-2402) Support AfterPane.elementGapAtMost() trigger and its combination with elementCountAtLeast()
Date Wed, 02 Sep 2020 17:08:37 GMT

    [ https://issues.apache.org/jira/browse/BEAM-2402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189485#comment-17189485
] 

Beam JIRA Bot commented on BEAM-2402:
-------------------------------------

This issue was marked "stale-P2" and has not received a public comment in 14 days. It is now
automatically moved to P3. If you are still affected by it, you can comment and move it back
to P2.

> 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
>            Priority: P3
>
> 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
(v8.3.4#803005)

Mime
View raw message