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

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

Github user chandnisingh commented on a diff in the pull request:

    
https://github.com/apache/incubator-apex-malhar/pull/237#discussion_r58965303
  
    --- Diff: 
library/src/test/java/org/apache/apex/malhar/lib/state/managed/ManagedStateImplTest.java
 ---
    @@ -147,9 +150,11 @@ public void testCommitted()
         Slice two = ManagedStateTestUtils.getSliceFor("2");
         commitHelper(one, two);
         Bucket.DefaultBucket defaultBucket = 
(Bucket.DefaultBucket)testMeta.managedState.getBucket(0);
    -    Assert.assertEquals("value of one", one, 
defaultBucket.getCommittedData().get(one).getValue());
    +    Assert.assertEquals("value of one",
    +        one, 
defaultBucket.getCommittedData().firstEntry().getValue().get(one).getValue());
     
    -    Assert.assertNull("value of two", 
defaultBucket.getCommittedData().get(two));
    +    Assert.assertNull("value of two",
    +        defaultBucket.getCommittedData().firstEntry().getValue().get(two));
    --- End diff --
    
    Same as above


> Managed State - value for a key is null when the bucket is bumped off state 
> and window data is still not committed
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: APEXMALHAR-2042
>                 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2042
>             Project: Apache Apex Malhar
>          Issue Type: Bug
>    Affects Versions: 3.4.0
>            Reporter: Chandni Singh
>            Assignee: Timothy Farkas
>
> When a bucket data is collected for transferring to data files and if the 
> bucket at the same time is triggered to free memory then for a brief time any 
> queries for a key in the bucket will not return any value. 



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

Reply via email to