From cb15c4157abae2e1bc65fd5a2990bc9111323388 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Heiko=20Thei=C3=9Fen?= Date: Thu, 9 Jan 2025 15:40:28 +0100 Subject: [PATCH] continue-on-error in batch --- docs/odata-protocol/odata-protocol.html | 2 +- docs/odata-protocol/odata-protocol.md | 7 +++++-- odata-protocol/8 Header Fields.md | 7 +++++-- 3 files changed, 11 insertions(+), 5 deletions(-) diff --git a/docs/odata-protocol/odata-protocol.html b/docs/odata-protocol/odata-protocol.html index dc4c035f..470a6b75 100644 --- a/docs/odata-protocol/odata-protocol.html +++ b/docs/odata-protocol/odata-protocol.html @@ -1020,7 +1020,7 @@

delta update, set-based update, or set-based delete to request that the service continue attempting to process changes after receiving an error.

If the service encounters any errors processing the request and returns a successful response code, then it MUST include a Preference-Applied response header containing the continue-on-error preference with an explicit value of true.

A service MAY specify support for the continue-on-error preference using an annotation with term Capabilities.BatchContinueOnErrorSupported, see OData-VocCap.

-

The continue-on-error preference SHOULD NOT be applied to individual requests within a batch.

+

The continue-on-error preference on a batch request refers to whether individual requests within a batch should be executed if others have failed. Whether an individual request that represents multiple operations should continue on error can instead be expressed through a continue-on-error preference on that individual request.

Note: The continue-on-error preference was named odata.continue-on-error in OData version 4.0. Services that support the continue-on-error preference SHOULD also support odata.continue-on-error for OData 4.0 clients and clients SHOULD use odata.continue-on-error for compatibility with OData 4.0 services.

diff --git a/docs/odata-protocol/odata-protocol.md b/docs/odata-protocol/odata-protocol.md index 42bd081a..bb41446d 100644 --- a/docs/odata-protocol/odata-protocol.md +++ b/docs/odata-protocol/odata-protocol.md @@ -1345,8 +1345,11 @@ using an annotation with term [`Capabilities.BatchContinueOnErrorSupported`](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Capabilities.V1.md#BatchContinueOnErrorSupported), see [OData-VocCap](#ODataVocCap). -The `continue-on-error` preference SHOULD NOT be applied to individual -requests within a batch. +The `continue-on-error` preference on a batch request refers to whether individual +requests within a batch should be executed if others have failed. Whether an +individual request that represents multiple operations should continue on error can +instead be expressed through a `continue-on-error` preference on that individual +request. Note: The `continue-on-error` preference was named `odata.continue-on-error` in OData version 4.0. Services that support diff --git a/odata-protocol/8 Header Fields.md b/odata-protocol/8 Header Fields.md index f7b7b985..e85c0b97 100644 --- a/odata-protocol/8 Header Fields.md +++ b/odata-protocol/8 Header Fields.md @@ -448,8 +448,11 @@ using an annotation with term [`Capabilities.BatchContinueOnErrorSupported`]($$$OData-VocCap$$$#BatchContinueOnErrorSupported), see [OData-VocCap](#ODataVocCap). -The `continue-on-error` preference SHOULD NOT be applied to individual -requests within a batch. +The `continue-on-error` preference on a batch request refers to whether individual +requests within a batch should be executed if others have failed. Whether an +individual request that represents multiple operations should continue on error can +instead be expressed through a `continue-on-error` preference on that individual +request. Note: The `continue-on-error` preference was named `odata.continue-on-error` in OData version 4.0. Services that support