[GitHub] [beam] damccorm opened a new issue, #17879: Don't leak garbage collection timers in GlobalWindow

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

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

   Consider the  transform:
     Window
       .into(new GlobalWindows())
       .triggering(
         Repeatedly.forever(
           AfterProcessingTime.pastFirstElementInPane().plusDelayOf(...)))
       .discardingFiredPanes()
   This is a common idiom for 'process elements bunched by arrival time'.
   Currently we create an end-of-window timer per key, which clearly will only fire if the pipeline is drained.
   Better would be to avoid creating end-of-window timers if there's no state which needs to be processed at end-of-window (ie at drain if the Global window).
   
   Imported from Jira [BEAM-175](https://issues.apache.org/jira/browse/BEAM-175). Original Jira may contain additional context.
   Reported by: mshields822.


-- 
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

[GitHub] [beam] damccorm closed issue #17879: Don't leak garbage collection timers in GlobalWindow

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

damccorm closed issue #17879: Don't leak garbage collection timers in GlobalWindow
URL: https://github.com/apache/beam/issues/17879


-- 
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

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