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
{{ message }}
This repository has been archived by the owner on Oct 11, 2024. It is now read-only.
In some cases, it would be very nice if we could ensure that multiple EntryUpdates would always be merged into the same MapRevision. The current API implicitly supports this by always merging things created in BatchUpdateUsers together, but this is not a good API if large numbers of updates were supplied to the batch API.
The text was updated successfully, but these errors were encountered:
gdbelvin
changed the title
Explicitly support multiple EntryUpdates being merged together.
Explicitly support EntryUpdate Atomicity
Mar 28, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In some cases, it would be very nice if we could ensure that multiple EntryUpdates would always be merged into the same MapRevision. The current API implicitly supports this by always merging things created in BatchUpdateUsers together, but this is not a good API if large numbers of updates were supplied to the batch API.
The text was updated successfully, but these errors were encountered: