You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ReplicatedMap Api Doc contains member only behaviours/requirements that client cannot meet due to its technical difference.
Most of the data providing methods like Collection<V> values(); promise to return a lazy data set backed by the map where changes to the map might be reflected in the set.
Members returns "a lazy set view of the mappings" as in api doc,
but client returns "a clone of the mappings" instead.
As all data exists on all members, such a behaviour easily provided. Whereas client provide simple proxy of a member and always return a clone of data.
The documentation should be review with this in mind.
The text was updated successfully, but these errors were encountered:
@asimarslan And member documentation is also not correct. It seems that server side implementation is refactored later and does not return lazy list/set anymore.
sancar
pushed a commit
to sancar/hazelcast
that referenced
this issue
Dec 15, 2017
ReplicatedMap Api Doc contains member only behaviours/requirements that client cannot meet due to its technical difference.
Most of the data providing methods like
Collection<V> values();
promise to return a lazy data set backed by the map where changes to the map might be reflected in the set.Members returns "a lazy set view of the mappings" as in api doc,
but client returns "a clone of the mappings" instead.
As all data exists on all members, such a behaviour easily provided. Whereas client provide simple proxy of a member and always return a clone of data.
The documentation should be review with this in mind.
The text was updated successfully, but these errors were encountered: