Write concern should not be encoded in aggregate unless $out is specified

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 0.1.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Running an aggregate without a $out stage on a collection that has a non-nil write concern yields the following error:

      command.Error{Code:72, Message:"Command does not support writeConcern", Labels:[]string(nil), Name:"InvalidOptions"}

      Change command/aggregate.go to only include write concern if $out is specified.

              Assignee:
              Divjot Arora (Inactive)
              Reporter:
              Divjot Arora (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: