[
https://issues.apache.org/jira/browse/BEAM-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132170#comment-17132170
]
Beam JIRA Bot commented on BEAM-279:
------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> 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: P2
> Labels: stale-P2
>
> 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)
