beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davor Bonaci (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (BEAM-279) Make sure we unit test bounded sessions
Date Fri, 17 Jun 2016 18:02:05 GMT

     [ https://issues.apache.org/jira/browse/BEAM-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Davor Bonaci updated BEAM-279:
------------------------------
    Component/s: sdk-java-core

> 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
>
> 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
(v6.3.4#6332)

Mime
View raw message