SEZ9 commented on issue #10443: URL: https://github.com/apache/seatunnel/issues/10443#issuecomment-6228443554
@goutamadwant Thanks for the revised tracker — the layout (merged first, then open PRs, then gaps) is fine, and the two new rows match what was agreed earlier in this thread: a focused `connector-jdbc` CockroachDB dialect and a bounded Couchbase source opened as a separate feature issue. Both rows should stay recorded as "Open PR" until they are reviewed and merged; both PRs currently have failing Build checks, so please address those in the PRs and keep implementation discussion there, with a link back here when they land. A few confirmations and asks before the description is updated: - CockroachDB row: the first slice should remain limited to demonstrated dialect behavior (quoted identifiers, `INSERT ... ON CONFLICT (configured keys) DO UPDATE`) with both physical-primary-key and explicitly-configured-unique-key cases proven against a real CockroachDB environment. Your comment says this was validated against CockroachDB and across the supported engines — please make sure that evidence is visible in the PR itself. No bundled driver dependency, standalone connector, CDC, or catalog redesign in this slice. - Couchbase row: linking the feature issue alongside the PR is correct. Keep the stated boundary explicit in that issue (read direction only, supported auth/TLS options, mapping and pagination/split behavior, checkpoint/recovery semantics, test boundary) so the tracker can point to one place for the scope. - DocumentDB sink row: agreed on the evidence gate you wrote out — the real-endpoint compatibility matrix must come before any PR, and if the gap turns out to be only per-job trust configuration, it should be an extension of the existing MongoDB sink rather than a separate sink. - The "Open gap" footnote is useful; please keep it so readers do not mistake "gap" for "unclaimed". @davidzollo On consolidation: I'd prefer to keep this issue separate from the broader external-source backlog and cross-link the two instead. This thread carries the database/storage connector matrix plus the ownership and compatibility evidence for the CockroachDB and Couchbase lanes, and merging it into the larger backlog would make that harder to follow. @goutamadwant Once the above is reflected, go ahead and update the description with this tracker. No ownership or assignment metadata is being changed by this comment. <!-- streview-comment:1807 --> -- 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]
