non-NULL write concern forces blocking read-response

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Duplicate
    • Priority: Major - P3
    • 0.7
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      I would like to have the option to force mongo to perform a best efforts write of my data but at this risk of inserting/updating too slowly - I don't care about the status response.

      It seems that the assumption is made that if write concern is non-NULL, I would obviously want to know the response - which in my case is not true.

      Maybe make this optional.

            Assignee:
            Gary Murakami (Inactive)
            Reporter:
            Mongo Mania
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: