apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Yan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (APEXMALHAR-2271) Special SpillableSetMultimap<K, Window.SessionWindow<K>> handling in ManagedState in SpillableSessionWindowedStorage
Date Tue, 27 Sep 2016 01:16:21 GMT

     [ https://issues.apache.org/jira/browse/APEXMALHAR-2271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

David Yan updated APEXMALHAR-2271:
----------------------------------
    Description: 
The problem with this data structure is that the key is not time based.
This poses a problem because we will have a problem purging.
One idea is to have `put` write the key and the window set to the timebucket that the latest
window in that set belongs to, which means possible duplication of the key and the window
set, and make `get` do a for loop on all time buckets to find the key. That way, purging based
on the time bucket can still be done.

  was:
The problem with this data structure is that the key is not time based.
This poses a problem because we will have a problem purging.
One idea is to have `put` write the key and the window set to the timebucket that the latest
window in that set belongs to, and make `get` do a for loop on all time buckets to find the
key. That way, purging based on the time bucket can still be done.


> Special SpillableSetMultimap<K, Window.SessionWindow<K>> handling in ManagedState
in SpillableSessionWindowedStorage
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: APEXMALHAR-2271
>                 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2271
>             Project: Apache Apex Malhar
>          Issue Type: Sub-task
>            Reporter: David Yan
>            Assignee: David Yan
>
> The problem with this data structure is that the key is not time based.
> This poses a problem because we will have a problem purging.
> One idea is to have `put` write the key and the window set to the timebucket that the
latest window in that set belongs to, which means possible duplication of the key and the
window set, and make `get` do a for loop on all time buckets to find the key. That way, purging
based on the time bucket can still be done.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message