Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ReplicatedMap API Doc reflects Member only behaviour #11707

Closed
asimarslan opened this issue Nov 1, 2017 · 1 comment
Closed

ReplicatedMap API Doc reflects Member only behaviour #11707

asimarslan opened this issue Nov 1, 2017 · 1 comment

Comments

@asimarslan
Copy link
Member

@asimarslan asimarslan commented Nov 1, 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.

@asimarslan asimarslan added this to the 3.9.1 milestone Nov 1, 2017
@tombujok tombujok modified the milestones: 3.9.1, 3.9.2 Nov 20, 2017
@sancar
Copy link
Member

@sancar sancar commented Nov 23, 2017

@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 added a commit to sancar/hazelcast that referenced this issue Dec 15, 2017
sancar added a commit to sancar/hazelcast that referenced this issue Dec 15, 2017
@sancar sancar self-assigned this Dec 15, 2017
sancar added a commit to sancar/hazelcast that referenced this issue Dec 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

4 participants
You can’t perform that action at this time.