[SERVER-62609] WriteConcernOptions should use the WriteConcernW type Created: 13/Jan/22 Updated: 29/Oct/23 Resolved: 01/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 5.3 Desired |
| Fix Version/s: | 5.3.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Matt Broadstone | Assignee: | Matt Broadstone |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Server Serverless 2022-01-24, Server Serverless 2022-02-07 | ||||
| Participants: | |||||
| Linked BF Score: | 150 | ||||
| Description |
|
The WriteConcernOptions type has three member variables which are mutually exclusive: wNumNodes, wMode, and now wTags. We also have a WriteConcernW type which wraps a std::variant of possible w value types. Use the WriteConcernW type in WriteConcernOptions, and update the server codebase to switch between variant value types when deciding how to interpret a write concern. |
| Comments |
| Comment by Githook User [ 01/Feb/22 ] |
|
Author: {'name': 'Matt Broadstone', 'email': 'mbroadst@mongodb.com', 'username': 'mbroadst'}Message: |