[
https://issues.apache.org/jira/browse/BEAM-2402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132400#comment-17132400
]
Beam JIRA Bot commented on BEAM-2402:
-------------------------------------
This issue is assigned but has not received an update in 30 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> 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: Pei He
> Priority: P2
> Labels: stale-assigned
>
> 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)
