Server::executeBulkWrite() should take a write concern

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Major - P3
    • 1.0.0-alpha1
    • Affects Version/s: 0.5.0
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Server::executeBulkWrite() currently takes no write concern and inherits from the client object. Should it take an optional write concern like its Manager counterpart? In PHPLIB, we need to select the primary manually for APIs that depend on wire version checking, and I'm thinking of a case where legacy index creation would want to ensure we only use w:1 on the insertion.

            Assignee:
            Jeremy Mikola (Inactive)
            Reporter:
            Jeremy Mikola (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: