You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@apex.apache.org by "Bhupesh Chawda (JIRA)" <ji...@apache.org> on 2017/03/14 11:21:41 UTC

[jira] [Updated] (APEXMALHAR-2408) Issues in correctness of get() for key search in ManagedTimeStateImpl

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

Bhupesh Chawda updated APEXMALHAR-2408:
---------------------------------------
    Summary: Issues in correctness of get() for key search in ManagedTimeStateImpl  (was: Validate correctness of get() for key search in ManagedTimeStateImpl)

> Issues in correctness of get() for key search in ManagedTimeStateImpl
> ---------------------------------------------------------------------
>
>                 Key: APEXMALHAR-2408
>                 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2408
>             Project: Apache Apex Malhar
>          Issue Type: Sub-task
>            Reporter: Chaitanya
>            Assignee: Chaitanya
>
> Below are the issues:
> 1) When the key searches all time buckets, not checking whether the time bucket is expired or not. 
> 2) CachedbucketMetas not cleared in DefaultBucket.freeMemory().
> 3) If the bucketed data is spill over multiple committed windows, firstKey of BucketMetaData is not changing after the second committed call.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)