You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Jeremy Ross (Jira)" <ji...@apache.org> on 2021/02/05 19:05:00 UTC
[jira] [Created] (CAMEL-16157) salesforce: Support composite's new
collateSubrequests option
Jeremy Ross created CAMEL-16157:
-----------------------------------
Summary: salesforce: Support composite's new collateSubrequests option
Key: CAMEL-16157
URL: https://issues.apache.org/jira/browse/CAMEL-16157
Project: Camel
Issue Type: Improvement
Components: camel-salesforce
Reporter: Jeremy Ross
From the [docs|https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/requests_composite.htm]:
{quote}Controls whether the API collates unrelated subrequests to bulkify them ({{true}}) or not ({{false}}).
When subrequests are collated, the processing speed is faster, but the order of execution is not guaranteed (unless there is an explicit dependency between the subrequests).
If collation is disabled, then the subrequests are executed in the order in which they are received.
Subrequests that contain valid HTTP headers are not collated.
In API version 49.0 and later, the default value is {{true}}. In version 48.0, the default value is {{false}}.
Subrequests can be collated if they meet these conditions: * The HTTP methods are the same.
* The API versions of the resources are the same.
* The parents of the resources are {{/sobjects}} resources.
* No more than five sObjects resources are present across a grouping of subrequests.{quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)