goutamadwant opened a new pull request, #11880:
URL: https://github.com/apache/seatunnel/pull/11880

   ### Purpose of this pull request
   
   Related to #9950.
   
   `MongodbScanFetchTask` currently converts every snapshot failure into 
`MongodbConnectorException` without retaining the original exception. This 
leaves only the generic `Illegal argument` message and hides whether the 
failure came from snapshot bounds, index hints, topology, TLS, authentication, 
or another MongoDB driver condition.
   
   This PR:
   
   - adds a cause-aware `MongodbConnectorException` constructor
   - preserves the original exception when snapshot execution fails
   - adds regression coverage at the snapshot task execution boundary
   - keeps the existing snapshot query, BSON bounds, hints, and checkpoint 
behavior unchanged
   
   ### Does this PR introduce _any_ user-facing change?
   
   Yes. MongoDB CDC snapshot failures now include the original driver exception 
in the cause chain. Successful snapshot behavior is unchanged.
   
   ### How was this patch tested?
   
   Verified with:
   
   - focused `MongodbScanFetchTaskTest` coverage
   - all 28 MongoDB CDC connector unit tests
   - `./mvnw -pl :connector-cdc-mongodb spotless:apply`
   - `./mvnw -pl :connector-cdc-mongodb -DskipTests verify`
   
   The existing MongoDB CDC E2E was also attempted locally. Testcontainers 
1.17.6 failed Docker environment discovery against Docker Engine 29.5.3 before 
any container or connector code ran.
   
   ### Check list
   
   * [x] No new Jar binary package is added.
   * [x] Documentation is not required for this diagnostic correction.
   * [x] This PR does not introduce an incompatible change.
   * [x] Connector distribution files are not affected because this does not 
add or modify connector packaging.


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