Sha256: 702bc09936a454a0059acd6edca49054376db2acb71249fa46785ea5a332a70f
Contents?: true
Size: 1.65 KB
Versions: 37
Compression:
Stored size: 1.65 KB
Contents
# Test that setting a default write concern does not add a write concern
# to the command sent over the wire.
# Test operations that require 3.2+ server, where findAndModify started
# to accept a write concern.
data:
- {_id: 1, x: 11}
- {_id: 2, x: 22}
collection_name: &collection_name default_write_concern_coll
database_name: &database_name default_write_concern_db
runOn:
- minServerVersion: "3.2"
tests:
- description: 'findAndModify operations omit default write concern'
operations:
- name: findOneAndUpdate
object: collection
collectionOptions: {writeConcern: {}}
arguments:
filter: {_id: 1}
update: {$set: {x: 1}}
- name: findOneAndReplace
object: collection
collectionOptions: {writeConcern: {}}
arguments:
filter: {_id: 2}
replacement: {x: 2}
- name: findOneAndDelete
object: collection
collectionOptions: {writeConcern: {}}
arguments:
filter: {_id: 2}
outcome:
collection:
name: *collection_name
data:
- {_id: 1, x: 1}
expectations:
- command_started_event:
command:
findAndModify: *collection_name
query: {_id: 1}
update: {$set: {x: 1}}
writeConcern: null
- command_started_event:
command:
findAndModify: *collection_name
query: {_id: 2}
update: {x: 2}
writeConcern: null
- command_started_event:
command:
findAndModify: *collection_name
query: {_id: 2}
remove: true
writeConcern: null
Version data entries
37 entries across 37 versions & 2 rubygems