-
Type: Spec Change
-
Resolution: Won't Do
-
Priority: Major - P3
-
None
-
Component/s: Change Streams, Retryability
-
Needed
SERVER-45505 adds a ResumableChangeStreamError label, which can be included on both aggregate and getMore command responses. The change stream spec says all errors on aggregate are considered fatal. Would it be possible for drivers to instead have a mechanism to resume aggregate attempts if the event of a transient error that has the new error label?
- split to
-
CDRIVER-4750 Consider resuming on aggregate for change streams
- Closed
-
CSHARP-4823 Consider resuming on aggregate for change streams
- Closed
-
CXX-2773 Consider resuming on aggregate for change streams
- Closed
-
GODRIVER-3028 Consider resuming on aggregate for change streams
- Closed
-
JAVA-5222 Consider resuming on aggregate for change streams
- Closed
-
MOTOR-1198 Consider resuming on aggregate for change streams
- Closed
-
NODE-5716 Consider resuming on aggregate for change streams
- Closed
-
PHPLIB-1293 Consider resuming on aggregate for change streams
- Closed
-
PYTHON-4013 Consider resuming on aggregate for change streams
- Closed
-
RUBY-3337 Consider resuming on aggregate for change streams
- Closed
-
RUST-1784 Consider resuming on aggregate for change streams
- Closed