SEZ9 commented on issue #10443:
URL: https://github.com/apache/seatunnel/issues/10443#issuecomment-6905396917

   @1328837476-hug Thanks for the update. Understood: #12907 is the Ingres JDBC 
dialect, now synced with `dev` at b5852a69f, and it is independent of the 
DocumentDB work tracked here. Nothing from this issue blocks it, and I agree 
with the earlier clarification from @yidaimi that its open items do not depend 
on the DocumentDB run. The remaining asks for #12907 stay where you stated 
them: a real-server validation against a licensed Ingres server and driver, and 
the sink gap. Please keep that discussion in the PR itself so this thread stays 
focused on DocumentDB, and post there once those two items have results to 
review.
   
   @yidaimi Thank you for the source validation matrix. The S01–S08 run against 
the live DocumentDB 5.0.2 TLS endpoint, built from `dev` at `928334411` with 
the RDS CA supplied only via `tls_ca_file`, covers exactly what was asked: 
per-job CA trust, the untrusted-CA failure, hostname verification with the 
explicit opt-out, and the `retryWrites(false)` enforcement. I consider the 
DocumentDB source validation closed for V1; stream mode, parallel splits and 
large collections are noted as not covered and can be tracked separately if 
someone needs them.
   
   What is still open on my side from this thread:
   
   - #13200 (omitted `buffer-flush.*` / `retry.*` defaults, with the 
`incompatible-changes.md` entry) and #13215 (`tls_ca_file` for the MongoDB 
sink) are the two focused PRs that came out of this issue. Both will be 
reviewed on their own merits; please ping on the PRs if either one needs 
another pass.
   - Once both are merged, I'll close this issue referencing them.
   
   <!-- streview-comment:2375 -->


-- 
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]

Reply via email to