Mailing-List: contact commits-help@beam.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@beam.apache.org
Date: Thu, 30 Mar 2017 19:48:42 +0000 (UTC)
From: "Kenneth Knowles (JIRA)" <jira@apache.org>
To: commits@beam.apache.org
Message-ID: <JIRA.13033548.1484090031000.168526.1490903322546@Atlassian.JIRA>
In-Reply-To: <JIRA.13033548.1484090031000@Atlassian.JIRA>
References: <JIRA.13033548.1484090031000@Atlassian.JIRA> <JIRA.13033548.1484090031057@jira-lw-us.apache.org>
Subject: [jira] [Commented] (BEAM-1261) State API should allow state to be
 managed in different windows
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 30 Mar 2017 19:48:47 -0000


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

Kenneth Knowles commented on BEAM-1261:
---------------------------------------

Fixed windows don't seem like a good fit for this use case or query 3. But I don't really know the details of how the query is implemented on Beam.

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