[
https://issues.apache.org/jira/browse/BEAM-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15857501#comment-15857501
]
Kenneth Knowles commented on BEAM-41:
-------------------------------------
Yes, I think that is a good idea. It would work well to do
{{readLater(Set<T>)}} or many (non-RPC) calls to {{readLater(T)}} and whenever
you called {{contains(T)}} it would do all the fetches. This all depends on the
cache a lot. I think it might be good to also have {{containsAny(Iterable<T>)}}
and {{containsAll(Iterable<T>)}} to be independent of the caching strategy.
> State for "Set" data, supporting efficient membership checks
> ------------------------------------------------------------
>
> Key: BEAM-41
> URL: https://issues.apache.org/jira/browse/BEAM-41
> Project: Beam
> Issue Type: New Feature
> Components: beam-model
> Reporter: Kenneth Knowles
> Assignee: Jingsong Lee
> Priority: Minor
> Labels: State
>
> Analogous to how BagState supports efficient blind writes, a SetState would
> support efficient membership checking without reading the entire set.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
