GitHub user amuldotexe edited a comment on the discussion: Iggy Connector Ecosystem Tracking
One thing that may help connector contributions is a short behavior checklist for every new connector PR. A very small version could be just these questions: 1. What is this connector: source, sink, or both, and what is its unit of data? 2. How does that unit map to an Iggy message? 3. For a source, what defines progress? For a sink, what defines external write identity? 4. What exact event counts as success, and where is the commit frontier? 5. In which failure windows can duplicates or loss happen? 6. What happens on restart? 7. What is the smallest failure-injection test that proves the claimed behavior? I think this would help because most connector review friction seems to come from behavioral boundaries rather than crate structure. We already have good implementation examples, especially on mapping, tracking, and restart behavior in sources. What is less consistent is making the delivery boundary and duplicate/loss windows explicit, especially for sinks. If this seems useful, I can turn it into: - a short connector behavior template in the docs - a review checklist for connector PRs - a 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]
