[
https://issues.apache.org/jira/browse/BEAM-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132084#comment-17132084
]
Beam JIRA Bot commented on BEAM-1261:
-------------------------------------
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.
> 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: New Feature
> Components: beam-model
> Reporter: Ben Chambers
> Priority: P2
> Labels: stale-P2
>
> 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
(v8.3.4#803005)
