Currently, mongos will drop the WCE on a no-op or successful create collection.
- causes
-
PYTHON-5198 test_encryption.TestAutomaticDecryptionKeys.test_03_invalid_keyid incorrect regex error
-
- Closed
-
- is caused by
-
SERVER-81189 Transform `create` requests in sharded cluster to `_shardSvrCreateCollection`
-
- Closed
-
- is related to
-
SERVER-98461 findAndModify where query does not have shard key does not return WCE on failure
-
- Closed
-
-
SERVER-96839 Pass writeConcern from UMCs into UMCTransaction
-
- Closed
-
-
SERVER-102101 TypeMismatch error on creating encrypted field for collection contains incorrect command name
-
- Closed
-
-
SERVER-104220 Router must take into account drop collection write concern error
-
- Closed
-
-
SERVER-106672 [v8.0] Add replicateSearchIndexCommand to list of all commands in write_concern_all_commands.js
-
- Needs Merge
-
-
SERVER-100937 Mongos must return WCE on dropIndexes
-
- Closed
-
-
SERVER-100938 Mongos must return WCE on createIndexes
-
- Closed
-
-
SERVER-100939 Mongos should return WCE on no-op setFeatureCompatibilityVersion
-
- Closed
-
-
SERVER-100942 setDefaultRWConcernDefault must return WCE
-
- Closed
-
-
SERVER-105528 Fix FLE2 findAndModify write concern error reporting in mongod
-
- Closed
-
- related to
-
SERVER-98461 findAndModify where query does not have shard key does not return WCE on failure
-
- Closed
-
-
SERVER-73553 Ensure mongos create command returns WriteConcern with higher precedence over NamespaceNotFound
-
- Closed
-
-
SERVER-84081 FLE2 write error hides write concern error
-
- Closed
-
-
SERVER-96839 Pass writeConcern from UMCs into UMCTransaction
-
- Closed
-
-
SERVER-99915 FLE2 findAndModify should also return WCE from transaction API result
-
- Closed
-
-
SERVER-102765 Create collection can be rollbacked and not retried on a Replica Set cluster
-
- Closed
-
-
SERVER-103664 Ensure Operations Are Quiesced Before Stopping Secondaries in mongos_writes_wait_for_write_concern_sharded_addl_crud_ops.js
-
- Closed
-
-
SERVER-104220 Router must take into account drop collection write concern error
-
- Closed
-
-
SERVER-105947 [v8.1] Change assertion in write_concern_all_commands.js for create timeseries collection
-
- In Code Review
-
-
SERVER-106672 [v8.0] Add replicateSearchIndexCommand to list of all commands in write_concern_all_commands.js
-
- Needs Merge
-
-
SERVER-100528 Investigate all commands that accept write concern for WCE handling
-
- Closed
-
-
SERVER-100937 Mongos must return WCE on dropIndexes
-
- Closed
-
-
SERVER-100938 Mongos must return WCE on createIndexes
-
- Closed
-
-
SERVER-100939 Mongos should return WCE on no-op setFeatureCompatibilityVersion
-
- Closed
-
-
SERVER-100942 setDefaultRWConcernDefault must return WCE
-
- Closed
-
-
SERVER-100943 abortTransaction must wait for write concern and return WCEs on failure
-
- Closed
-
-
SERVER-101386 Test all commands that accept write concern against timeseries collections
-
- Closed
-
-
SERVER-101387 Test all commands that accept write concern against FLE collections
-
- Closed
-
-
SERVER-102024 Always set lastOp to systemLastOp on no-op writes
-
- Closed
-
-
SERVER-102391 Mongos must return WCE as a top-level error for create collection
-
- Closed
-
-
SERVER-105528 Fix FLE2 findAndModify write concern error reporting in mongod
-
- Closed
-
-
SERVER-106577 [v8.0] Prepare SPM-4070 8.0 branch for release
-
- Closed
-
-
SERVER-102571 Check against WriteConcernError category when processing QE transactions
-
- Closed
-