SEZ9 commented on issue #10443: URL: https://github.com/apache/seatunnel/issues/10443#issuecomment-6818042947
@yidaimi thanks for running the matrix against a live DocumentDB 5.0.2 TLS endpoint and publishing the config, evidence excerpts and `run-matrix.sh` — that is exactly the kind of material the "separate sink gap" item was waiting on. Your conclusion matches what we see in the code: endpoint validation, auth and write semantics behave as expected, and the only real gap is per-job trust construction (`tlsCAFile` / `tlsAllowInvalidCertificates` in the URI being ignored by the driver, leaving a JVM-global trust store as the only working route). Splitting that into a focused defaults bug + fix PR and a separate `tls_ca_file` feature issue with one shared client-settings builder (writer, catalog/save-mode client and dry-run validator) plus trusted/untrusted-CA TLS tests is the right shape; nothing further is needed from you on this thread for the sink gap, and each of those trackers will be reviewed on its own. One ask: since you already have a working DocumentDB cluster and a reproducible script, would you be willing to run the source connector from this issue's PR against the same endpoint (read path, `tls_ca_file`, `retryWrites(false)`) and post the config + log excerpt here in the same redacted form? That would close the remaining "real-server validation" item. @1328837476-hug noted that the rerun for `02312129a` passed and that `37b5dbdc1` has a green fork build (run 41861666431). With the sink gap now tracked separately, the only item still open on your side is that real-server validation — if yidaimi's setup can be reused, please coordinate here so we only need one round; otherwise let us know what you can run locally and I'll confirm what evidence is sufficient. <!-- streview-comment:2295 --> -- 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]
