DanielCarter-stack opened a new pull request, #11731:
URL: https://github.com/apache/seatunnel/pull/11731

   ## Summary
   
   Improve the MongoDB CDC source connector documentation by adding five new 
task-based examples that were missing or under-documented. The changes mirror 
the structure already used for the other CDC connectors and use realistic 
configurations aligned with the e2e test fixtures under 
`seatunnel-e2e/seatunnel-connector-v2-e2e/connector-cdc-mongodb-e2e/`.
   
   ### Added task examples
   
   - **CDC data write to another MongoDB** — uses `MongoDB-CDC` as the source 
and the `MongoDB` sink to mirror a collection into another cluster.
   - **Startup from a specific timestamp** — shows how to skip the snapshot and 
resume the change stream from a known epoch timestamp using `startup.mode = 
timestamp` and `startup.timestamp`.
   - **Using the SRV connection URI** — demonstrates connecting to Atlas-style 
clusters via `mongodb+srv://` directly in the `hosts` option without an extra 
`connection.options` block.
   - **Heartbeat and resume token maintenance** — shows how 
`heartbeat.interval.ms` keeps the change stream open on low-traffic collections 
so the resume token does not expire across checkpoint restores.
   - **Reading from multiple MongoDB sources** — fans in CDC streams from two 
MongoDB clusters into one sink, aligned with the existing 
`mongodb_multi_source_a.conf` / `mongodb_multi_source_b.conf` e2e fixtures.
   
   ### Notes
   
   - The existing `Source Options` table, data type mapping, availability 
settings, change stream section, metadata fields, and CDC examples are 
unchanged.
   - English and Chinese docs are kept in sync; the Chinese doc adds the same 
five sections.
   - No source code, version markers, or supported-version tables are touched.


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