[OLINGO-1381] Odata client core adding ContentID as single for every ODataBatchRequest present in BatchManager

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: (Java) V4 4.6.0
• Fix Version/s: (Java) V4 4.9.0
• Component/s: odata4-client
• Labels: batch clientCore nonTransact olingo
• Assignee: mibo
• Reporter: kritisha
• Created: 06/Aug/19 12:29
• Updated: 04/Mar/22 04:51
• Resolved: 04/Mar/22 04:51

Description

Olingo client core currently adds the content-Id as Single for every request in a Odata Batch which is not in adherance with the Odata spec  see http://docs.oasis-open.org/odata/odata/v4.01/cs01/part1-protocol/odata-v4.01-cs01-part1-protocol.html#_Toc505771282 

Here the spec clearly mentions: 

“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.”

However in Olingo we are setting the ContentId as a string "_SINGLE" see https://github.com/apache/olingo-odata4/blob/master/lib/client-core/src/main/java/org/apache/olingo/client/core/communication/request/batch/ODataSingleResponseItem.java._ 

Our OData server(in this case Microsoft Dynamics Rest Api) is having a check for this content-ID uniqueness and hence the batch requests are failing. This is a blocking issue for using OData batching (without changesets) in olingo client core Jar.