mattcasters commented on issue #2838:
URL: https://github.com/apache/hop/issues/2838#issuecomment-6763121274

   Beta plan for Bulk API support. The five existing transforms stay on the 
SOAP Partner API.
   
   Bulk API 2.0 is a different protocol and a different lifecycle: create a 
job, upload one CSV, close it, poll, then download result files that are not in 
input order. A "use bulk" switch on Insert, Update, Upsert, Delete, or Input 
would fork error handling and row lifetime inside those transforms. The SOAP 
path still matters for small synchronous calls and for Get fields.
   
   Two experimental transforms in the existing Salesforce plugin:
   
   * **Salesforce bulk load (experimental)** (`SalesforceBulkLoad`) — insert, 
update, upsert, delete, and hard delete through Bulk API 2.0 ingest.
   * **Salesforce bulk input (experimental)** (`SalesforceBulkInput`) — `query` 
and `queryAll` through Bulk API 2.0 query.
   
   Both reuse the `salesforce-connection` metadata (OAuth, JWT, or a 
username/password session id sent as a bearer token). No new Salesforce SDK. 
Bulk API 1.0 is out of scope. The names say experimental. The plugin ids stay 
stable so a pipeline saved during the beta does not need a later rename.
   
   Tests do not need a Salesforce org. Unit tests stub the public REST contract 
with WireMock, which this module already uses. The docker-compose integration 
suite gets a small Bulk API 2.0 stub that stores the uploaded CSV and returns 
success and failed results, plus an `integration-tests/salesforce` project. A 
scratch org remains a possible later check. It needs a Dev Hub and does not fit 
the unattended compose suite.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to