-
Notifications
You must be signed in to change notification settings - Fork 3
Atomic Operations
Jan Wiemer edited this page Dec 29, 2020
·
6 revisions
Getting a single object from the store is generally an atomic operation. All modifications done by other concurrent transactions are either committed or not. Technically the access on the value is synchronized with the commit operation on this store (only on the current store not all others). However if we access a whole collection of values this operation is no longer atomic by default. Between fetching two objects of the collection another transaction may commit nev values for those. This may lead to the phantom read phenomenon discussed in the Transactions chapter.
Next Chapter: Metadata Access