[ODATA-1130] JSON Batch and continue-on-error - OASIS Technical Committees Issue Tracker

XML

Word

Printable

Details

Type: Improvement
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: V4.01_CSD03
Fix Version/s: V4.01_CS01
Component/s: JSON Format, Protocol
Labels:
None
Environment:

Applied

Proposal:

Hide

allow "continue-on-error=false" and "continue-on-error=true". "continue-on-error" implies true. If continue-on-error is not specified, then default is false in multipart mixed, true in json. In multipartmixed, continue-on-error=false means stop if any statement fails. In json it means that a best effort is requested not to spend cycles on further processing if a failure occurs outside of dependency groups because the client is not interested in the result.

Show
allow "continue-on-error=false" and "continue-on-error=true". "continue-on-error" implies true. If continue-on-error is not specified, then default is false in multipart mixed, true in json. In multipartmixed, continue-on-error=false means stop if any statement fails. In json it means that a best effort is requested not to spend cycles on further processing if a failure occurs outside of dependency groups because the client is not interested in the result.
Resolution:

Hide

https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/4.01%20spec/ABNF/odata-abnf-construction-rules.txt?op=diff&rev=1108
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/4.01%20spec/ABNF/odata-abnf-testcases.xml?op=diff&rev=1108

https://www.oasis-open.org/committees/download.php/62018/odata-v4.01-wd04-part1-protocol-2017-11-13-redlined.docx
https://www.oasis-open.org/committees/download.php/62016/odata-json-format-v4.01-wd04-2017-11-10-redlined.docx

Show
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/4.01%20spec/ABNF/odata-abnf-construction-rules.txt?op=diff&rev=1108 https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/4.01%20spec/ABNF/odata-abnf-testcases.xml?op=diff&rev=1108 https://www.oasis-open.org/committees/download.php/62018/odata-v4.01-wd04-part1-protocol-2017-11-13-redlined.docx https://www.oasis-open.org/committees/download.php/62016/odata-json-format-v4.01-wd04-2017-11-10-redlined.docx

Description

The JSON Format specifcation states in http://docs.oasis-open.org/odata/odata-json-format/v4.01/csprd03/odata-json-format-v4.01-csprd03.html#sec_ProcessingaBatchRequest that

The service MAY process the individual requests and atomicity groups within a batch request in any order that is compatible with the dependencies expressed with the dependsOn name/value pair. Processing stops on the first error unless the continue-on-error preference is specified.

This makes batch processing somewhat non-deterministic.

Also it is not clear what "stop processing" means:

If the service chose to process independent groups of requests in parallel, will only groups stop that contain a failing individual request?
What is contained in the array of responses for "skipped"/"unprocessed" individual requests?

Do we need continue-on-error at all for JSON Batch requests?
If yes: does it only apply to subsequent requests within "dependency chains"?
Or do we intentionally leave this up to the service implementation and thus non-deterministic?

Attachments

Activity

People

Assignee:

Ralf Handl

Reporter:

Ralf Handl

Watchers:

2 Start watching this issue

Dates

Created:

07/Nov/17 3:57 PM

Updated:

23/Nov/17 9:39 AM

Resolved:

09/Nov/17 4:50 PM