Possibly this could be handled by rewindowing and the current semantics. If not, maybe treat state like a side input with its own windowing and window mapping fn.
On Jan 10, 2017 3:14 PM, "Ben Chambers (JIRA)" <j...@apache.org> wrote: > Ben Chambers created BEAM-1261: > ---------------------------------- > > Summary: State API should allow state to be managed in > different windows > Key: BEAM-1261 > URL: https://issues.apache.org/jira/browse/BEAM-1261 > Project: Beam > Issue Type: Bug > Components: beam-model, sdk-java-core > Reporter: Ben Chambers > Assignee: Kenneth Knowles > > > For example, even if the elements are being processed in fixed windows of > an hour, it may be desirable for the state to "roll over" between windows > (or be available to all windows). > > It will also be necessary to figure out when this state should be deleted > (TTL? maximum retention?) > > Another problem is how to deal with out of order data. If data comes in > from the 10:00 AM window, should its state changes be visible to the data > in the 9:00 AM window? > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) >
