[
https://issues.apache.org/jira/browse/BEAM-2402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17179880#comment-17179880
]
Beam JIRA Bot commented on BEAM-2402:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> 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: P2
> Labels: stale-P2
>
> 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)
