[
https://issues.apache.org/jira/browse/BEAM-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15953449#comment-15953449
]
Etienne Chauchot commented on BEAM-1261:
----------------------------------------
Well, actually, the original query in the PR was implemented using fixed
windowing of 10 seconds but IMHO it might make more sense to use sliding
windows to provide updates of "who as been selling in the US for the last
hour". But either ways, state will not go through windows for now, so I will
implement it with a global window. As there are already others queries
(query7, query8, query10) to illustrate fixed windowing, it is OK to illustrate
only state (+ timers) in query3.
> 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, sdk-java-core
> Reporter: Ben Chambers
>
> 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.15#6346)
