GitHub user amuldotexe edited a comment on the discussion: Iggy Connector Ecosystem Tracking
One thing that may help connector contributions is a very small behavior section in each connector PR. Something along these lines: 1. What defines progress for this connector, or what defines external write identity? 2. What exact event counts as success, and where is the commit frontier? 3. After failure or restart, what can be replayed, duplicated, or lost? 4. What is the smallest failure-injection test that proves that behavior? The reason I think this helps is that most connector review friction seems to come from these boundaries, not from crate layout. A small example: - for a source, the important question is usually: when does progress advance relative to send-to-Iggy? - for a sink, the important question is usually: when does the external system durably acknowledge a write relative to offset commit? If that is written down early, a lot of later review comments become easier. If this seems useful, I can turn it into: - a short connector behavior template in the docs - a review checklist for connector PRs - a small source-first conformance checklist, then a sink-side version after that GitHub link: https://github.com/apache/iggy/discussions/2756#discussioncomment-16033487 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
