[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: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Driver Compliance: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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. |