-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 0.5.0
-
Component/s: 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.
- is depended on by
-
PHPLIB-109 Refactor write command methods into operation classes
- Closed
-
PHPLIB-85 Legacy index creation should specify a write concern
- Closed
- related to
-
PHPC-187 getServer()->executeBulkWrite() uses wrong WriteConcern
- Closed
-
CDRIVER-786 Using w=-1 write concern causes "invalid response_to" cursor errors
- Closed