Fix semantics for write concern provenance when implicit default is used

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.0.0-rc1, 5.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Fully Compatible
    • v5.0
    • Repl 2021-05-31
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      We set the write concern provenance to be customDefault even when using the implicit default because of this line. customeDefaultWasApplied should be set based on the DefaultWriteConcernSource. We should update this in strategy.cpp similarly.

            Assignee:
            Huayu Ouyang
            Reporter:
            Samyukta Lanka
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: