DanielCarter-stack commented on issue #10357: URL: https://github.com/apache/seatunnel/issues/10357#issuecomment-3764660500
<!-- code-pr-reviewer --> Thank you for the feature request. After analyzing the current codebase, Azure CosmosDB Source Connector does not exist in SeaTunnel—there is no `connector-cosmosdb` or `connector-azure*` module under `seatunnel-connectors-v2/`. The proposed design aligns well with SeaTunnel standards: - `table_list` pattern is already used by JDBC (`JdbcSourceOptions.java:42-46`), StarRocks, and Paimon connectors - `table_path` format is supported by `TablePath.of()` in `seatunnel-api/src/main/java/org/apache/seatunnel/api/table/catalog/TablePath.java:63` - NoSQL connectors like Amazon DynamoDB (`seatunnel-connectors-v2/connector-amazondynamodb/`) can serve as reference However, the Azure CosmosDB Java SDK dependency is not currently present in the codebase, and incremental extraction with Change Feed (CDC) will require new implementation. To help the community prioritize this feature, please clarify: 1. Should SQL API and MongoDB API be implemented simultaneously, or phased (starting with SQL API)? 2. For Change Feed mode, should it use CosmosDB native SDK or integrate with SeaTunnel's CDC framework? 3. Beyond `master_key` authentication, do you need `managed_identity` or token-based credential support? -- 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]
