[GitHub] [beam] damccorm opened a new issue, #17868: Make sure we unit test bounded sessions

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

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

   A few customers have been using Window.into(Sessions...) and of course quickly realize they are exposed to unbounded sessions.
   
   We should have unit tests to confirm various combinations of AfterPane.elementCountAtLeast and AfterProcessingTime... correctly force sessions to be broken apart.
   
   We should also check this all works with repeated messages with the same timestamp (since they will create the exact same session window and can thus see trigger state from previous sessions).
   
   At some point we may may flow into reworking bounded sessions to be done directly rather than via Sessions plus triggers.
   
   Imported from Jira [BEAM-279](https://issues.apache.org/jira/browse/BEAM-279). 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 #17868: Make sure we unit test bounded sessions

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

damccorm closed issue #17868: Make sure we unit test bounded sessions
URL: https://github.com/apache/beam/issues/17868


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