Uploaded image for project: 'OASIS Open Data Protocol (OData) TC'
  1. OASIS Open Data Protocol (OData) TC
  2. ODATA-306

Batch Request processing: Define server behavior, if one or more request(s) didn't succeed

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: V4.0_WD01
    • Fix Version/s: V4.0_WD01
    • Component/s: Protocol
    • Labels:
      None
    • Environment:

      [Proposed]

    • Proposal:
      Hide

      The server MUST process the N components of the Batch in the order received.
      It continues processing until
      the first request fails or the first change set fails.
      If the processing is terminated after the component M (M<N) the response contains only the first M components; the N-M not processed components are not part of the response.
      This is the standard processing behavior.

      The client can request by a prefer header odata.continue-on-failure that the server should process all requests and change-sets not stopping if any failure occurs.

      Accepted: https://www.oasis-open.org/committees/download.php/48752/odata-meeting-31_on-20130404-minutes.html#odata-306

      Show
      The server MUST process the N components of the Batch in the order received. It continues processing until the first request fails or the first change set fails. If the processing is terminated after the component M (M<N) the response contains only the first M components; the N-M not processed components are not part of the response. This is the standard processing behavior. The client can request by a prefer header odata.continue-on-failure that the server should process all requests and change-sets not stopping if any failure occurs. Accepted: https://www.oasis-open.org/committees/download.php/48752/odata-meeting-31_on-20130404-minutes.html#odata-306
    • Resolution:
      Hide

      Applied: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/48762/odata-core-v4.0-wd01-part1-protocol-current-2013-4-5MP.docx

      Accepted: https://www.oasis-open.org/committees/download.php/49026/odata-meeting-34_on-20130425_26-F2F-minutes.html#odata-306

      Show
      Applied: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/48762/odata-core-v4.0-wd01-part1-protocol-current-2013-4-5MP.docx Accepted: https://www.oasis-open.org/committees/download.php/49026/odata-meeting-34_on-20130425_26-F2F-minutes.html#odata-306

      Description

      The order of Change Sets and non-Change-Set operations in a Batch request is significant as a service MUST process the N components of the Batch in the order received.
      Currently only the behavior is described, if the last operation in sequence fails.
      How should the server react, if the first ChangeSet processing fails or if the first non-Change-Set operation fails? Should he terminated the processing or should he continue the processing? How is the Batch Respond Format defined, if the processing is terminated?

      The requests must be processed in sequence, so it would make sense to stop after the first failed request or change sets as a default behaviour.

        Attachments

          Activity

            People

            • Assignee:
              mikep Michael Pizzo (Inactive)
              Reporter:
              martinzurmuehl Martin Zurmuehl
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: