-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.4.10, 3.6.2, 3.7.1
-
Component/s: Replication, Write Ops
-
Replication
-
ALL
-
-
18
The update command will validate updates for modified immutable fields, $-prefixed fields, BSON depth, etc. When updates are performed through applyOps, this validation is not performed.
- is related to
-
SERVER-32305 Able to create document with array as _id using applyOps
- Backlog
-
SERVER-32941 applyOps command inserts documents without ever calling fixDocumentForInsert()
- Backlog
-
SERVER-35248 Use ReplOperation IDL to reject malformed operations in applyOps command
- Backlog
-
SERVER-36195 applyOps accepts invalid op types
- Backlog
-
SERVER-36593 applyOps may not include _id in oplog entry
- Backlog
-
SERVER-32934 Full document replacement can change type of _id
- Closed
-
SERVER-36950 applyOps createIndexes command with non-existent UUID reports success
- Closed
-
SERVER-36955 applyOps accepts invalid UUIDs for the create command
- Closed
-
SERVER-30798 Disallow running applyOps with a renameCollection entry that renames across databases
- Backlog
-
SERVER-27096 applyOps should validate its ops to ensure idempotency
- Backlog
- related to
-
SERVER-43329 renameCollectionWithinDBForApplyOps should not use temp collections on primary
- Backlog
-
SERVER-53674 Do not run applyOps commands in the fuzzer
- Closed
-
SERVER-58247 Using createIndexes in applyOps with the oplog application mode set on primary should uassert, not fassert
- Closed
-
SERVER-36263 Bypassing operation validation in applyOps should require special privilege
- Closed