[
https://issues.apache.org/jira/browse/BEAM-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15857498#comment-15857498
]
Kenneth Knowles commented on BEAM-42:
-------------------------------------
This is interesting. The way you link it with {{ReadableState}} is smart. But
maybe we should just not extend it and instead just use {{iterateLater()}} and
{{iterator()}}.
I think you might want {{Iterable<V> get(Iterable<K>)}} to do a bulk get. You
might consider a {{getLater(K)}} or {{getLater(Iterable<K>)}} that would mean
that later when you actually use {{get}} all the queued fetches can be
performed in a single RPC and loaded into the local cache, but if it overflows
the cache it is still worse than just a bulk get.
> State for "Map" data, supporting efficient key lookup, etc.
> -----------------------------------------------------------
>
> Key: BEAM-42
> URL: https://issues.apache.org/jira/browse/BEAM-42
> Project: Beam
> Issue Type: New Feature
> Components: beam-model
> Reporter: Kenneth Knowles
> Assignee: Jingsong Lee
> Priority: Minor
> Labels: State
>
> Analogous to BagState's blind writes, and SetState's efficient membership
> check, MapState would add efficient key lookup and mutation, and other
> Map-related operations.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
