-
Type: Task
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Component/s: None
-
None
The Write Concern specification has documented, for all drivers, how to interpret an unacknowledged write concern. Many of our drivers have subtle variations on what is spec'ed. This shouldn't be a backwards breaking change for any, but may be a behavioral change for some in the sense that what was previously considered unacknowledged might now be considered acknowledged. You'll need to note in your release notes if this is the case.
Please validate your driver or create a linked ticket.
- depends on
-
CDRIVER-908 Ensure spec compliance for unacknowledged write concerns.
- Closed
-
CSHARP-1436 Ensure spec compliance for unacknowledged write concerns.
- Closed
-
CXX-696 Ensure spec compliance for unacknowledged write concerns.
- Closed
-
CXX-697 Ensure spec compliance for unacknowledged write concerns.
- Closed
-
JAVA-2003 Ensure spec compliance for unacknowledged write concerns.
- Closed
-
NODE-579 Ensure spec compliance for unacknowledged write concerns.
- Closed
-
PHPC-449 Ensure spec compliance for unacknowledged write concerns.
- Closed
-
PYTHON-1001 Ensure spec compliance for unacknowledged write concerns.
- Closed
-
RUBY-1050 Ensure spec compliance for unacknowledged write concerns.
- Closed
-
RUST-9 Ensure spec compliance for unacknowledged write concerns.
- Closed
- has to be done after
-
NODE-579 Ensure spec compliance for unacknowledged write concerns.
- Closed
- is related to
-
SERVER-19496 Latency optimized write API
- Closed