beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ben Chambers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-1261) State API should allow state to be managed in different windows
Date Thu, 30 Mar 2017 20:20:42 GMT

    [ https://issues.apache.org/jira/browse/BEAM-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949730#comment-15949730
] 

Ben Chambers commented on BEAM-1261:
------------------------------------

I believe this use case can be handled with a global window (for example) where things are
stored, and once both the person and auction have been encountered, a timer is set to eventually
clear them out. Why are windows necessary for this case?

> 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)

Mime
View raw message