SEZ9 commented on issue #10443: URL: https://github.com/apache/seatunnel/issues/10443#issuecomment-5747238688
@goutamadwant thanks for keeping the tracker current. On the Amazon DocumentDB sink row: the status you wrote is accurate — the ask remains the sanitized, deterministic compatibility matrix for the existing MongoDB sink against a real DocumentDB-compatible TLS endpoint before any implementation PR. Please keep the row as "Pending — compatibility evidence required before extending the existing MongoDB sink" until that evidence is posted here. To restate what the matrix needs to cover so we can close the loop in one pass: - Current MongoDB sink options used and the driver version. - CA/hostname/auth behavior observed against the DocumentDB-compatible endpoint. - Where the failure actually sits: trust construction, endpoint validation, or write semantics. - What the DocumentDB source does differently with its isolated SSLContext that the sink cannot do today. Local MongoDB/TLS fixtures are fine as supporting unit coverage, but they are not sufficient on their own to establish the compatibility boundary. If the matrix confirms that the only gap is per-job trust configuration, the path forward is the backward-compatible MongoDB-sink extension with explicit CA/hostname semantics, no global trust-all behavior and no bundled dependency — not a separate DocumentDB sink. Once you post the matrix, I can update the row to reflect the agreed scope. <!-- streview-comment:1183 --> -- 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]
