amuldotexe opened a new issue, #2892: URL: https://github.com/apache/iggy/issues/2892
We already have a good integration harness and several source-specific tests, but the same behavioral questions keep coming back in review. For sources, the real friction is usually around: - when progress advances - what happens if send to Iggy fails - what happens on restart - when mark/delete style side effects happen We already have parts of this in a few places: - #2579 added Postgres sink/source integration tests - #2739 / the recent MongoDB source work ended up being mostly about source behavior, not crate layout It may be worth having a small shared source suite on top of the current harness. Pareto here just means: not exhaustive, just the few tests that catch most source mistakes. Possible first scope: - progress does not advance before send to Iggy succeeds - failed send is replayed on the next poll - restart resumes from committed state - post-read side effects happen only after commit - the duplicate/replay window is explicit This would not replace backend-specific tests. It would just give new source connectors a small behavioral baseline. ## Acceptance criteria - A reusable source-side test helper or suite exists on top of the current harness - At least one existing source connector is wired into it - A short doc shows how a new source 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]
