mattcasters opened a new pull request, #9410:
URL: https://github.com/apache/hop/pull/9410

   ## Summary
   
   Adds two experimental transforms to the existing Salesforce plugin for [Bulk 
API 
2.0](https://developer.salesforce.com/docs/atlas.en-us.api_asynch.meta/api_asynch/bulk_api_2_0.htm).
 The SOAP Input, Insert, Update, Upsert, and Delete transforms are unchanged.
   
   * **Salesforce bulk load (experimental)** (`SalesforceBulkLoad`) inserts, 
updates, upserts, deletes, or hard-deletes one object through an ingest job.
   * **Salesforce bulk input (experimental)** (`SalesforceBulkInput`) runs 
`query` or `queryAll` and reads the CSV result pages.
   
   Bulk API 2.0 is a different lifecycle from the partner API: create a job, 
upload one CSV, close it, poll, then download result files that are not in 
input order. A flag on the existing transforms would mix that with the 
synchronous `SaveResult` path, so these are separate transforms. Both reuse the 
`salesforce-connection` metadata. An OAuth token is sent as a bearer token. A 
username/password connection uses the SOAP session id the same way. There is no 
new Salesforce SDK.
   
   The transforms are local-engine only. Beam and Spark refuse them by plugin 
id.
   
   Fixes #2838.
   
   ## Testing
   
   * `plugins/tech/salesforce` unit tests, including CSV rules, reversed result 
matching, the session id used as a bearer token, and the REST job flow against 
WireMock.
   * Beam `BeamPipelineEngineSupportsTest` and Spark 
`HopPipelineMetaToSparkConverterTest` for the engine bans.
   * The Bulk API stub in 
`docker/integration-tests/salesforce-mock/bulk_api.py` was exercised directly: 
insert with a failed row, reversed success rows, two query pages, and HTTP 401.
   
   The `integration-tests/salesforce` project runs those same cases through Hop 
against the stub 
(`docker/integration-tests/integration-tests-salesforce.yaml`). That compose 
project was not executed inside the Hop integration image.


-- 
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