[
https://issues.apache.org/jira/browse/BEAM-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17145663#comment-17145663
]
Beam JIRA Bot commented on BEAM-279:
------------------------------------
This issue was marked "stale-P2" and has not received a public comment in 14
days. It is now automatically moved to P3. If you are still affected by it, you
can comment and move it back to P2.
> 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
>
> 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.3.4#803005)
