Define atomicity #2107

HeikoTheissen · 2025-07-24T08:47:12Z

mikepizzo · 2025-07-30T16:01:55Z

odata-protocol/11.4 Data Modification.md

@@ -13,6 +13,18 @@ the [`return`](#Preferencereturnrepresentationandreturnminimal) preference.
 A [success response](#SuccessResponses) indicates that data have been modified,
 regardless of whether the requested content could be returned.

+Data modification requests guarantee _atomicity_ in the following sense:
+When the request completes successfully, every subsequent request observes a state of the system


remove "successfully"

Suggested change

When the request completes successfully, every subsequent request observes a state of the system

When the request completes, every subsequent request observes a state of the system

mikepizzo · 2025-07-30T16:03:19Z

odata-protocol/11.4 Data Modification.md

+while the data modification request is still being executed.
+
+A transactional service is a service that protects against seeing such partial changes.
+But for services that do not require this degree of transactional consistency,


Suggested change

But for services that do not require this degree of transactional consistency,

For services that do not require this degree of transactional consistency,

mikepizzo · 2025-07-30T16:13:11Z

odata-protocol/11.4 Data Modification.md

@@ -1287,6 +1299,9 @@ If an individual change fails due to a failed dependency, it MUST be
 annotated with the term [`Core.DataModificationException`]($$$OData-VocCore$$$#DataModificationException) and SHOULD specify
 a `responseCode` of `424` ([Failed Dependency](#ResponseCode424FailedDependency)).

+Regardless of the `continue-on-error` preference, the collection update must happen


Continue-on-error necessarily means non-atomic. Atomicity means all or none of the user's intent is carried out.

In the absence of continue-on-error, the operation must complete in an atomic manner.

odata-protocol/11.4 Data Modification.md

mikepizzo · 2025-07-30T16:16:03Z

odata-protocol/11.4 Data Modification.md

+a state of the system where the changes have been carried out only partially
+while the data modification request is still being executed.
+
+A transactional service is a service that protects against seeing such partial changes.


Might have to have a better term than "Transactional" -- a transactional service may have different isolation levels.

mikepizzo · 2025-08-13T15:30:17Z

odata-protocol/11.4 Data Modification.md

+Data modification requests guarantee _atomicity_ in the following sense:
+When the request completes, every subsequent request observes a state of the system
+in which either all or none of the changes have been carried out.
+But depending on how a service makes this guarantee, clients MAY observe


Suggested change

But depending on how a service makes this guarantee, clients MAY observe

Depending on how a service makes this guarantee, clients MAY observe

mikepizzo · 2025-08-13T15:37:45Z

odata-protocol/11.4 Data Modification.md

+a state of the system where the changes have been carried out only partially
+while the data modification request is still being executed.
+
+If required, services can offer an isolation level that protects against seeing such partial changes.


Suggested change

If required, services can offer an isolation level that protects against seeing such partial changes.

Where required, services can offer an isolation level that protects against seeing such partial changes.

mikepizzo · 2025-08-13T15:42:17Z

odata-protocol/11.4 Data Modification.md

+For services that do not require this degree of transactional consistency,
+it is up to the service implementation to define rollback semantics to undo any changes that
+may have been applied before another change failed and thereby guarantee this all-or-nothing requirement.


Suggested change

For services that do not require this degree of transactional consistency,

it is up to the service implementation to define rollback semantics to undo any changes that

may have been applied before another change failed and thereby guarantee this all-or-nothing requirement.

It is up to the service implementation to rollback any changes that may have been applied before another change failed and thereby guarantee this all-or-nothing requirement.

mikepizzo · 2025-08-13T15:44:09Z

odata-protocol/11.4 Data Modification.md

+a state of the system where the changes have been carried out only partially
+while the data modification request is still being executed.


Suggested change

a state of the system where the changes have been carried out only partially

while the data modification request is still being executed.

a state of the system where the changes have been carried out only partially

while the data modification request is still being executed, including changes that may later be rolled back.

mikepizzo · 2025-08-13T15:58:40Z

odata-json-format/19 Batch Requests and Responses.md

+atomicity group or else apply none of them (atomicity in the sense of
+[#OData-Protocol#Atomicity]).


Suggested change

atomicity group or else apply none of them (atomicity in the sense of

[#OData-Protocol#Atomicity]).

atomicity group or else apply none of them. See [#OData-Protocol#Atomicity] for details on visibility of atomic changes.

mikepizzo · 2025-08-13T19:10:53Z

odata-protocol/11.7 Batch Requests.md

-define rollback semantics to undo any requests within a change set that
-may have been applied before another request in that same change set
-failed and thereby apply this all-or-nothing requirement. The service
+or else apply none of them (atomicity in the sense of [section ##Atomicity]). The service


Suggested change

or else apply none of them (atomicity in the sense of [section ##Atomicity]). The service

or else apply none of them. See [#OData-Protocol#Atomicity] for details on visibility of atomic changes. The service

Define atomicity

bd4d024

mikepizzo reviewed Jul 30, 2025

View reviewed changes

odata-protocol/11.4 Data Modification.md Show resolved Hide resolved

mikepizzo reviewed Jul 30, 2025

View reviewed changes

HeikoTheissen added 3 commits July 31, 2025 09:07

TC 2025-07-30

788b806

Atomicity in JSON batch requests

04559ce

Atomicity in multipart batch requests

b2902a7

mikepizzo reviewed Aug 13, 2025

View reviewed changes

Mention isolation levels

39f1d73

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Define atomicity #2107

Define atomicity #2107

Uh oh!

HeikoTheissen commented Jul 24, 2025

Uh oh!

mikepizzo Jul 30, 2025

Uh oh!

mikepizzo Jul 30, 2025

Uh oh!

mikepizzo Jul 30, 2025 •

edited

Loading

Uh oh!

mikepizzo Jul 30, 2025

Uh oh!

Uh oh!

mikepizzo Jul 30, 2025

Uh oh!

mikepizzo Aug 13, 2025

Uh oh!

mikepizzo Aug 13, 2025

Uh oh!

mikepizzo Aug 13, 2025

Uh oh!

mikepizzo Aug 13, 2025

Uh oh!

mikepizzo Aug 13, 2025

Uh oh!

mikepizzo Aug 13, 2025

Uh oh!

Uh oh!

	When the request completes successfully, every subsequent request observes a state of the system
	When the request completes, every subsequent request observes a state of the system

	But for services that do not require this degree of transactional consistency,
	For services that do not require this degree of transactional consistency,

	But depending on how a service makes this guarantee, clients MAY observe
	Depending on how a service makes this guarantee, clients MAY observe

	If required, services can offer an isolation level that protects against seeing such partial changes.
	Where required, services can offer an isolation level that protects against seeing such partial changes.

		a state of the system where the changes have been carried out only partially
		while the data modification request is still being executed.

		atomicity group or else apply none of them (atomicity in the sense of
		[#OData-Protocol#Atomicity]).

	or else apply none of them (atomicity in the sense of [section ##Atomicity]). The service
	or else apply none of them. See [#OData-Protocol#Atomicity] for details on visibility of atomic changes. The service

Define atomicity #2107

Are you sure you want to change the base?

Define atomicity #2107

Uh oh!

Conversation

HeikoTheissen commented Jul 24, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mikepizzo Jul 30, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

mikepizzo Jul 30, 2025 •

edited

Loading