The jstest created in SERVER-33339 left out test cases that define whether a dbVersion is sent for:
- copydb
- createIndexes
- drop (collection)
- dropDatabase
- listCollections
- renameCollection
- validate
These commands should be tested separately, since they cannot be tested by using the profiler.
Additionally,
- update
- delete
should be tested separately, since they are batched and the profiler only captures individual updates/deletes within the batch, so it loses any fields on the outer command.
- depends on
-
SERVER-33499 Consolidate CurOp initialization
-
- Backlog
-
- is duplicated by
-
SERVER-34406 blacklist database_and_shard_versioning_all_commands.js from the config stepdown suite
-
- Closed
-
- is related to
-
SERVER-33339 add jstest that documents and verifies whether each command sends a database version
-
- Closed
-