-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Removing serializable option from datastore Transaction. #1294
Removing serializable option from datastore Transaction. #1294
Conversation
In v1beta3 we opted to only expose serializable which is a stronger form of isolation. I think in v1beta2 if you want to remove the option you need to force it to be set to serializable (the default is snapshot). Also, I'm not sure if you've seen it, but here are the (whitelisted) release notes: https://cloud.google.com/datastore/v1beta3/release-notes |
LGTM. I never saw the point in |
@pcostell that URL 404s for me. |
9ad1f2d
to
0a407f6
Compare
Thanks @pcostell. Can you also add daniel.j.hermes@gmail.com? (I can see it with my corp email, but seldom have corp access.) @tseaver After seeing Patrick's comments and the whitelist, I think it's best to set the isolation level always to serializable. PTAL |
This is in advance of the option being removed in v1beta3. Since in v1beta3: > All transactions are now serializable we set the isolation to always be serializable.
1cb8a3d
to
2ceace5
Compare
@tseaver are we LGTM with the update to |
LGTM: setting explicitly in the protobuf makes the behavior forward compatible. |
Removing serializable option from datastore Transaction.
Thanks |
This is in advance of the option being removed in v1beta3. Since in v1beta3:
we set the isolation to always be serializable.
@pcostell Is this "safe" to do as prep for the version upgrade?
Also, is there an equivalent replacement in
v1beta3
? AFAICT the isolation level is just gone.