The bulk API execute function will throw an error if using an invalid write concern against a 2.6 server.
Examples:
bulk.execute({w:{a:1}})
bulk.execute({w:2}) // for a standalone mongod
This is not a server issue but an inconsistency in the shell bulk API.
- is related to
-
RUBY-731 On write concern error, bulk insert raises error but still inserts
-
- Closed
-
- related to
-
SERVER-15119 Accept a named "writeConcern" option for bulk.execute
-
- Closed
-