[DRIVERS-440] Improve testing around default writeConcern Created: 17/Jan/18 Updated: 21/Feb/23 Resolved: 21/Feb/23 |
|
| Status: | Closed |
| Project: | Drivers |
| Component/s: | None |
| Fix Version/s: | None |
| Type: | Epic | Priority: | Major - P3 |
| Reporter: | Rathi Gnanasekaran | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Driver Changes: | Not Needed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Server Compat: | 4.3, 4.4 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Quarter: | FY20Q3 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Upstream Changes Summary: | This feature has been asked for quite some time by Cloud, so tagging that team. Docs, because it will have to be documented. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Start date: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Cost Threshold %: | 100 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Driver Compliance: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
Epic Summary SummaryThe existing tests for writeConcern imply that an empty document is a valid writeConcern to send to the server. In fact, the default writeConcern is no writeConcern (i.e. don't send the writeConcern field at all). This has come up in the past related to drivers accidentally overriding getLastErrorDefaults. It is coming up again in relation to PM-900. There have been two bugs filed and fixed in drivers related to this - Please add tests to ensure that drivers don't add the writeConcern option with an empty document to write commands when the application has not specified a write concern. Lead : Jeremy Spec test changeSPEC-1352 introduces a new spec test format for the read/write concern tests, mostly equivalent to existing transactions/CRUD spec tests, to verify that write operations do not include a default write concern: |
| Comments |
| Comment by PM Bot [ 24/Feb/22 ] |
|
If you are not logged in, you can view the tickets in this epic by following this link. |