DanielCarter-stack commented on issue #10357: URL: https://github.com/apache/seatunnel/issues/10357#issuecomment-3764259389
<!-- code-pr-reviewer --> Thanks for the feature request. After checking the codebase, SeaTunnel does not currently have an Azure Cosmos DB connector. I can confirm this is a valid new connector request, and your proposed `table_list` + `table_path` design aligns well with existing patterns in the project. The configuration approach you suggested matches patterns used by other connectors: - JDBC connector's `TABLE_LIST` parameter (`connector-jdbc/src/main/java/org/apache/seatunnel/connectors/seatunnel/jdbc/config/JdbcSourceOptions.java:42-46`) - Paimon connector's multi-table config parsing using `TablePath` (`connector-paimon/src/main/java/org/apache/seatunnel/connectors/seatunnel/paimon/config/PaimonSourceTableConfig.java:52-65`) - `TablePath.of()` utility supports the `database.container` format you proposed (`seatunnel-api/src/main/java/org/apache/seatunnel/api/table/catalog/TablePath.java:49-70`) Before implementation begins, could you clarify: 1. Which API should be prioritized: SQL API or MongoDB API? 2. Should Change Feed (CDC) mode be included in the initial release or deferred to a follow-up? 3. Are there specific Azure SDK versions or dependencies that should be aligned with existing SeaTunnel dependencies? -- 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]
