-
Type: Task
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
The current implementation of getLastError in mongos does not correctly aggregate write concern errors (any write concern error always aborts the entire GLE).
Better supporting this mode is needed for backwards compatibility and so the bulk api is able to downconvert against mongos 2.6 correctly (though this should be rare and weird).
- related to
-
SERVER-12274 Fail-fast on invalid WriteConcern options in write commands
- Closed