[DRIVERS-266] Ensure spec compliance for unacknowledged write concerns. Created: 05/Oct/15  Updated: 15/Apr/19  Resolved: 21/Jun/16

Status: Closed
Project: Drivers
Component/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Craig Wilson Assignee: Barrie Segal
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on CDRIVER-908 Ensure spec compliance for unacknowle... Closed
depends on CSHARP-1436 Ensure spec compliance for unacknowle... Closed
depends on CXX-696 Ensure spec compliance for unacknowle... Closed
depends on CXX-697 Ensure spec compliance for unacknowle... Closed
depends on JAVA-2003 Ensure spec compliance for unacknowle... Closed
depends on NODE-579 Ensure spec compliance for unacknowle... Closed
depends on PHPC-449 Ensure spec compliance for unacknowle... Closed
depends on PYTHON-1001 Ensure spec compliance for unacknowle... Closed
depends on RUBY-1050 Ensure spec compliance for unacknowle... Closed
depends on RUST-9 Ensure spec compliance for unacknowle... Closed
Gantt Dependency
has to be done after NODE-579 Ensure spec compliance for unacknowle... Closed
Related
is related to SERVER-19496 Latency optimized write API Closed
Driver Compliance:
Key Status/Resolution FixVersion
CSHARP-1436 Done 2.2
CXX-696 Done legacy-1.1.0-rc0
PHPC-449 Done 1.0.0
PYTHON-1001 Cannot Reproduce
CDRIVER-908 Done 1.2.0
SCALA-215 Won't Fix
CXX-697 Done
JAVA-2003 Done 3.2.0
PERL-578 Done
RUBY-1050 Done 2.2.0
NODE-579 Done 2.0.45
PHP-1510 Done 1.6.14
RUST-9 Won't Do

 Description   

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.


Generated at Thu Feb 08 08:21:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.