Inconsistent application of read/write concern in mongoc_collection_aggregate

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 1.5.0
    • Affects Version/s: None
    • Component/s: libmongoc
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      As discussed on slack:

      • mongoc_collection_aggregate is documented as applying write_concern from the collection but does not appear to so do
      • mongoc_collection_aggregate takes a BSON options documents like other "_with_opts" helpers, but does not follow the same API pattern: allowing write_concern and/or read_concern in options as well as falling back to the collection defaults

            Assignee:
            Hannes Magnusson (Inactive)
            Reporter:
            David Golden
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: