amuldotexe opened a new issue, #2893: URL: https://github.com/apache/iggy/issues/2893
We already have sink-specific integration tests today, but they are mostly backend-specific. The harder review questions keep being about the sync boundary itself. For sinks, the real questions are usually: - when do we call an external write successful - what happens on partial failure - what can be replayed, duplicated, or lost on restart - what makes replay safe We already have parts of this in a few places: - #2592 and #2595 added e2e tests for Elasticsearch and Iceberg sinks - #2815 (MongoDB sink) had to make partial failure behavior and non-silent failure paths explicit It may be worth having a small shared sink suite on top of the current harness. Pareto here just means: not exhaustive, just the few tests that catch most sink mistakes. Possible first scope: - partial external failure is not reported as full success - restart behavior is explicit and tested - duplicate/loss windows are explicit - deterministic write identity is tested where relevant This would not replace connector-specific happy-path tests. It would just give new sink connectors a small behavioral baseline. ## Acceptance criteria - A reusable sink-side test helper or suite exists on top of the current harness - At least one existing sink connector is wired into it - A short doc shows how a new sink connector plugs into it -- 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]
