[GitHub] [beam] kennknowles opened a new issue, #18329: Support AfterPane.elementGapAtMost() trigger and its combination with elementCountAtLeast()

[GitBox <gi...@apache.org>]

kennknowles opened a new issue, #18329:
URL: https://github.com/apache/beam/issues/18329

   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
   
   Imported from Jira [BEAM-2402](https://issues.apache.org/jira/browse/BEAM-2402). Original Jira may contain additional context.
   Reported by: peihe0@gmail.com.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org