[jira] [Comment Edited] (APEXMALHAR-2276) ManagedState: value of a key does not get over-written in the same time bucket

["Chandni Singh (JIRA)" <ji...@apache.org>]

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

Chandni Singh edited comment on APEXMALHAR-2276 at 10/6/16 5:28 PM:
--------------------------------------------------------------------

I don't see a problem. In Scenario A, it is evident right at the time of insertion that update is old and is ignored.
In Scenario B, it is unknown at the time of insertion that update is old.

Which is why I mentioned, that the client needs to do a get() and then put(). 


was (Author: csingh):
I don't see a problem. In Scenario A, it is evident right at the time of insertion that update is old and is ignored.
In Scenario B, it is unknown at the time of insertion that update is old.

Which is why I mentioned, that the client needs to do a get() and then put(). 

ManagedStateImpl and ManagedTimeStateImpl are not for maintaining time series in memory. 

> ManagedState: value of a key does not get over-written in the same time bucket
> ------------------------------------------------------------------------------
>
>                 Key: APEXMALHAR-2276
>                 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2276
>             Project: Apache Apex Malhar
>          Issue Type: Bug
>            Reporter: Siyuan Hua
>            Assignee: Chandni Singh
>             Fix For: 3.6.0
>
>
> For example:
> ManagedTimeUnifiedStateImpl mtus;
> mtus.put(10000, key1, val1)
> mtus.put(10000, key1, val2)
> mtus.get(10000, key1).equals(val2) will return false



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