You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@olingo.apache.org by "mibo (Jira)" <ji...@apache.org> on 2022/02/17 05:35:00 UTC

[jira] [Assigned] (OLINGO-1554) Olingo V4 - Uniqueness of Content-ID in batch request

     [ https://issues.apache.org/jira/browse/OLINGO-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

mibo reassigned OLINGO-1554:
----------------------------

    Assignee: mibo

> Olingo V4 - Uniqueness of Content-ID in batch request
> -----------------------------------------------------
>
>                 Key: OLINGO-1554
>                 URL: https://issues.apache.org/jira/browse/OLINGO-1554
>             Project: Olingo
>          Issue Type: Bug
>          Components: odata4-client
>    Affects Versions: (Java) V4 4.8.0
>         Environment: SAP_GWFND 7.54 SP4
>            Reporter: Kai Stritzelberger
>            Assignee: mibo
>            Priority: Blocker
>              Labels: V4, batch, clientCore, odata4, olingo, olingo4
>         Attachments: 0001-OLINGO-1554-Fix-for-Uniqueness-of-Content-ID-in-requ.patch
>
>
> Currently, the Olingo client core uses an ascending index for the Content-ID header value which is unique in the individual changeset but not in the complete batch request when using BatchManager.addChangeset API.
> This leads to problems with SAPs OData V4 services and is not correct according to the OData V4 spec:
> 11.7.7.1 Multipart Batch Request Body
> "[...] Each body part representing an operation in the change set MUST specify a Content-ID header with a request identifier that is unique within the batch request. [...]"



--
This message was sent by Atlassian Jira
(v8.20.1#820001)