DanielLeens commented on issue #10443: URL: https://github.com/apache/seatunnel/issues/10443#issuecomment-5618442542
Thanks for narrowing the Amazon DocumentDB question to per-job CA/TLS configuration. Please do not start a separate DocumentDB sink: current dev already has a DocumentDB source, and a parallel sink would duplicate the MongoDB write path before the compatibility boundary is established. The next step is a sanitized, deterministic compatibility matrix for the existing MongoDB sink against a real DocumentDB-compatible TLS endpoint: current sink options and driver version; CA/hostname/auth behavior; whether the failure is trust construction, endpoint validation, or write semantics; and what the DocumentDB source does differently. Local MongoDB/TLS fixtures are useful unit coverage but cannot prove DocumentDB compatibility. If that matrix confirms only a missing per-job trust configuration, the smallest candidate would be a backward-compatible MongoDB-sink extension with explicit CA/hostname semantics, no global trust-all behavior, no bundled dependency, and focused tests. Please post that evidence before opening an implementation PR. -- 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]
