Loading...

XML

Word

Printable

JSON

Epic Link:
CSOT
Upstream Changes Summary:
Hide

DRIVERS-3391:
Summary of necessary driver changes

Clarify that when withTransaction retry backoff and jitter would exceed a client-side timeout—either the legacy withTransaction retry time limit or, if CSOT is in use, the CSOT deadline—drivers must raise a timeout error derived from the original error, wrapping that error as the cause, instead of rethrowing the raw error directly.

Commits for syncing spec/prose tests
(and/or refer to an existing language POC if needed)

https://github.com/mongodb/specifications/commit/e83452055d60b27bc943900504ba926bea57690e
Show
DRIVERS-3391 : Summary of necessary driver changes Clarify that when withTransaction retry backoff and jitter would exceed a client-side timeout—either the legacy withTransaction retry time limit or, if CSOT is in use, the CSOT deadline—drivers must raise a timeout error derived from the original error, wrapping that error as the cause, instead of rethrowing the raw error directly. Commits for syncing spec/prose tests (and/or refer to an existing language POC if needed) https://github.com/mongodb/specifications/commit/e83452055d60b27bc943900504ba926bea57690e
Confidence Status:
None

Documentation Changes Summary:

Hide

1. What would you like to communicate to the user about this feature?
2. Would you like the user to see examples of the syntax and/or executable code and its output?
3. Which versions of the driver/connector does this apply to?

Show
1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?

This ticket was split from DRIVERS-3391, please see that ticket for a detailed description.

split from

DRIVERS-3391 Clarify expected error if backoff exceeds CSOT's deadline in withTransaction