DanielLeens commented on issue #10443: URL: https://github.com/apache/seatunnel/issues/10443#issuecomment-4618059647
Thanks for writing the V1 boundary down this explicitly. The Core API-only scope and the out-of-scope list are much clearer now. The one part I would still narrow further before the first PR is `source + sink` together. For a brand-new connector, having both directions in the first contribution is still broader than we usually want for an initial review, even with a clear non-goal list. The review surface becomes much larger at once: config shape, type handling, read semantics, write semantics, test coverage, and failure behavior all arrive in one patch. My recommendation is: 1. pick **either** `sink only` or `source only` for the first PR 2. keep it Azure Cosmos **Core API only**, exactly as you described 3. keep catalog discovery, schema inference, container creation, managed identity auth, change feed, continuation tokens, and exactly-once semantics out of the first slice If the sink side is already the more complete piece, opening a **sink-only** first PR would be a very reasonable path. Then the source side can follow as a separate PR once the first slice lands. If you want to work on the source side first instead, please also keep #10357 linked so the tracking stays clear there. A small first PR will move much faster in review than trying to land both directions together. Once you choose the first slice, please open the PR against `dev` and link it back here. -- 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]
