Improve WriteConcernOptions to differentiate uninitialized from 'usedDefault'

XMLWordPrintableJSON

    • Query Optimization
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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'.

              Assignee:
              [DO NOT USE] Backlog - Query Optimization
              Reporter:
              Charlie Swanson
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: