Uploaded image for project: 'Teiid'
  1. Teiid
  2. TEIID-5545

Odata V4 Batch processing does not work as teiid/olingo rejects "Accept: multipart/mixed" request header

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 12.2
    • 11.2
    • OData
    • None
    • Hide

      Use OpenUI5/ SapUI5 OData V4 model with the following config in Manifest.xml

      "t": {
				"dataSource": "test",
				"settings": {
					"earlyRequests" : true,
					"autoExpandSelect": true,
					"operationMode": "Server",
					"groupId": "$auto",
					"synchronizationMode": "None"
				}
			},

      groupId = $auto is the relevant config option which means use batch processing

      Show
      Use OpenUI5/ SapUI5 OData V4 model with the following config in Manifest.xml "t" : { "dataSource" : "test" , "settings" : { "earlyRequests" : true , "autoExpandSelect" : true , "operationMode" : "Server" , "groupId" : "$auto" , "synchronizationMode" : "None" } }, groupId = $auto is the relevant config option which means use batch processing
    • Hide

      no workaround found yet

      Show
      no workaround found yet

    Description

      When using Teiid together with SAPUI5/OpenUI5 Odata V4 model, batch processing does not work as Teiid rejects the "Accept: multipart/mixed" header. The issue has been described in

      https://developer.jboss.org/message/986421#986421

      It has been stated that Olingo in general does support multipart messages and it was recommended to remove the header from the request.

      https://developer.jboss.org/message/986425#986425

      Unfortunately this seems to be not easily possible when using the SAPUI5 framework. I addressed the issue in the SAPUI5 forum under the following issue:

      https://github.com/SAP/openui5/issues/2288

      The result of this discussion was, that the header is valid for the send content. As I am no expert in the topic I do not really have an opinion on that. However,

      https://www.w3.org/Protocols/rfc1341/7_2_Multipart.html

      suggests that the header is required. So I am not sure if it is correct or an error to reject the message. However, if Olingo can process the content, it would be great to have a fix for the accept header, or alternatively a config option to enable handling of the Accept header in a way that Olingo processes these data.

      Attachments

        Activity

          People

            rhn-engineering-rareddy Ramesh Reddy
            cjohn001 Christoph John (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: