beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenneth Knowles (JIRA)" <>
Subject [jira] [Commented] (BEAM-170) Session windows should not be identified by their bounds
Date Thu, 26 May 2016 16:25:13 GMT


Kenneth Knowles commented on BEAM-170:

Yes, creating a new type of window for sessions that includes a UUID is a natural solution.
Would you like to take this ticket? :-)

> Session windows should not be identified by their bounds
> --------------------------------------------------------
>                 Key: BEAM-170
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-core
>            Reporter: Kenneth Knowles
> Today, if two session windows for the same key have the same bounds, they are considered
the same window. This is an accident. It is not intended that any session windows are considered
equal except via the operation of merging them into the same session.
> A risk associated with this behavior is that two windows that happen to coincide will
share per-window-and-key state rather than evolving separately and having their separate state
reconciled by state merging logic. These code paths are not required to be coherent, and in
practice they are not.
> In particular, if the trigger for a session window ever finishes, then subsequent data
in a window with the same bounds will be dropped, whereas if it had differed by a millisecond
it would have created a new session, ignoring the previously closed session.

This message was sent by Atlassian JIRA

View raw message