DanielLeens commented on issue #10753: URL: https://github.com/apache/seatunnel/issues/10753#issuecomment-5602979625
I rechecked current `dev` and the complete open PR set. SeaTunnel has a Salesforce source implementation and shared client, but no sink implementation or active Salesforce sink PR. @goutamadwant posted the first complete Salesforce sink plan on September 8, so that is the active claim. The first slice should use bounded REST sObject Collections upserts for one object with a required external ID, inspect every per-record result, and surface partial, validation, permission, timeout, and retry exhaustion failures. It must flush before checkpoint completion, document at-least-once delivery, and not claim exactly-once execution of Salesforce side effects. Keep delete support, Bulk API 2.0 ingestion, multi-object routing, and catalog work out of this PR. @ClaireLytt, please choose a different unclaimed connector so work does not duplicate the active Salesforce sink slice. No labels or formal assignees were changed. -- 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]
