-
Type: Bug
-
Resolution: Unresolved
-
Priority: Unknown
-
None
-
Component/s: Retryability
-
Needed
-
In the previous specification for executing retryable writes, there is an edge case where the server only returns errors with the "NoWritesPerformed" error label. If this happens, the following block is unreachable:
if (originalError is not DriverException && ! originalError.hasErrorLabel("NoWritesPerformed")) { previousError = originalError; }
In this case, the previousError that will be propagated to the user will be "null". In reality, this routine should propagate the first NoWritesPerformed-labeled error.
- documents
-
DRIVERS-2504 Extend Retryable Writes "NoWritesPerformed" Test Coverage
- Backlog
- is depended on by
-
GODRIVER-2651 Operation returns nil error if original and retry have `NoWritesPerformed` label
- Closed
- is related to
-
GODRIVER-2651 Operation returns nil error if original and retry have `NoWritesPerformed` label
- Closed
-
DRIVERS-2327 Propagate Original Error for Write Errors Labeled NoWritesPerformed
- Implementing
- split to
-
CSHARP-4441 Break NoWritesPerformed-Only Error Sequence
- Backlog
-
CXX-2619 Break NoWritesPerformed-Only Error Sequence
- Backlog
-
RUST-1552 Break NoWritesPerformed-Only Error Sequence
- Backlog
-
PHPLIB-1048 Break NoWritesPerformed-Only Error Sequence
- Closed
-
RUBY-3190 Break NoWritesPerformed-Only Error Sequence
- Closed
-
CDRIVER-4531 Break NoWritesPerformed-Only Error Sequence
- Closed
-
GODRIVER-2670 Break NoWritesPerformed-Only Error Sequence
- Closed
-
MOTOR-1071 Break NoWritesPerformed-Only Error Sequence
- Closed
-
NODE-4864 Break NoWritesPerformed-Only Error Sequence
- Closed
-
PYTHON-3535 Break NoWritesPerformed-Only Error Sequence
- Closed
-
JAVA-4827 Break NoWritesPerformed-Only Error Sequence
- Closed