[SERVER-41444] Improve WriteConcernOptions to differentiate uninitialized from 'usedDefault' Created: 31/May/19  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Internal Code, Querying
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Charlie Swanson Assignee: Backlog - Query Optimization
Resolution: Unresolved Votes: 0
Labels: neweng, qopt-team
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-23923 Agg $out writeConcern not enforced wh... Closed
Assigned Teams:
Query Optimization
Participants:

 Description   

In SERVER-23923 we discovered that the WriteConcernOptions attached to the OperationContext only report to have 'usedDefault' if the operation called 'extractWriteConcern'. This is not done for some requests which don't need to write, for example an OP_QUERY request. To aid users of WriteConcernOptions in understanding these subtleties, we proposed adding more states for WriteConcernOptions to be in. Something like 'kUninitialized', 'kUsedDefault', 'kExplicitlySet'.


Generated at Thu Feb 08 04:57:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.