apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APEXMALHAR-2271) Special SpillableSetMultimap<K, Window.SessionWindow<K>> handling in ManagedState in SpillableSessionWindowedStorage
Date Tue, 15 Nov 2016 00:51:59 GMT

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

ASF GitHub Bot commented on APEXMALHAR-2271:
--------------------------------------------

GitHub user siyuanh opened a pull request:

    https://github.com/apache/apex-malhar/pull/495

    APEXMALHAR-2271 Implement a multimap with time extract from value

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/siyuanh/apex-malhar APEXMALHAR-2271

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/apex-malhar/pull/495.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #495
    
----
commit df304e3d62da165c4b9e83ffffef5d9304aa328d
Author: Siyuan Hua <hsy541@apache.org>
Date:   2016-11-15T00:50:55Z

    APEXMALHAR-2271 Implement a multimap with time extract from value

----


> 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: Siyuan Hua
>
> 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