[
https://issues.apache.org/jira/browse/BEAM-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17545961#comment-17545961
]
Danny McCormick edited comment on BEAM-279 at 6/3/22 3:36 PM:
--------------------------------------------------------------
This issue has been migrated to [https://github.com/apache/beam/issues/17868]
was (Author: JIRAUSER282469):
This isn't actually real, but this issue has been migrated to
https://github.com/apache/beam/issues/17868
> Make sure we unit test bounded sessions
> ---------------------------------------
>
> Key: BEAM-279
> URL: https://issues.apache.org/jira/browse/BEAM-279
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-core
> Reporter: Mark Shields
> Priority: P3
> Labels: Clarified
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
