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

Doc: Hazelcast supports REPEATABLE_READ instead of READ_COMMITTED #337

pveentjer opened this issue Oct 26, 2012 · 0 comments


None yet
1 participant
Copy link

commented Oct 26, 2012

The documentation should be updated. The documentation currently states that Hazelcast supports read committed isolation level. But when a map entry is read within a transaction, it automatically is locked, the actual isolation level is REPEATABLE_READ since no one can make a change to the data that has been read.

From a correctness point of view there is nothing wrong with over-delivering (we provide a higher isolation level than we promise). I think it is wise to explain what isolation level hazelcast is supporting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.