-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Component/s: Retryability, Transactions
-
None
-
Needed
-
Summary
Add a missing test case to assert that a driver does not retry a read when in a transaction. This would have prevented JAVA-4684 regression.
The requirement is in the retryable reads specification in the when not to allow retry section.
Motivation
Who is the affected end user?
Driver authors
How likely is it that this problem or use case will occur?
This seems like an easy bug for a driver to have or introduce, and it's hard to detect since it depends on a server failure at just the right time
If the problem does occur, what are the consequences and how severe are they?
Applications won't get the benefit of the convent transaction API's automatic retry mechanism if a driver has this bug
Is this issue urgent?
Yes, since we want to fix the Java driver bug and need a test to assert correct behavior.
Is this ticket required by a downstream team?
No
Is this ticket only for tests?
It's a missing test of required behavior
- related to
-
JAVA-4684 Read operations in transactions are incorrectly retried
- Closed
- split to
-
CXX-2552 Add test that reads are not retried in a transaction
- Closed
-
PHPLIB-918 Add test that reads are not retried in a transaction
- Closed
-
CDRIVER-4436 Add test that reads are not retried in a transaction
- Closed
-
CSHARP-4267 Add test that reads are not retried in a transaction
- Closed
-
GODRIVER-2502 Add test that reads are not retried in a transaction
- Closed
-
JAVA-4686 Add test that reads are not retried in a transaction
- Closed
-
MOTOR-1000 Add test that reads are not retried in a transaction
- Closed
-
NODE-4465 Add test that reads are not retried in a transaction
- Closed
-
PYTHON-3368 Add test that reads are not retried in a transaction
- Closed
-
RUBY-3063 Add test that reads are not retried in a transaction
- Closed
-
RUST-1418 Add test that reads are not retried in a transaction
- Closed