[
https://issues.apache.org/jira/browse/APEXMALHAR-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431168#comment-15431168
]
bright chen commented on APEXMALHAR-2193:
-----------------------------------------
All the update in fact only apply to in memory data. For the data already
written to file(s), only the most recent file take effect. When get the value
of a key, first get value from memory, then get value from files ordered by the
time desc.
I had a solution for memory management, see PR
https://github.com/apache/apex-malhar/pull/375 and jira
https://issues.apache.org/jira/browse/APEXMALHAR-2190. Right now, the reset()
method was called by client code( after
AbstractManagedStateImpl.beforeCheckpoint(long) called), it probably need to
integrate with State management.
> Implement SpillableByteArrayListMultimapImpl.remove(@Nullable Object key,
> @Nullable Object value)
> -------------------------------------------------------------------------------------------------
>
> Key: APEXMALHAR-2193
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2193
> Project: Apache Apex Malhar
> Issue Type: Sub-task
> Reporter: David Yan
> Assignee: David Yan
>
> This is needed by SpillableSessionWindowedStorage. It needs a way to remove
> the session window given the key in its internal keyToWindowsMap
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)