-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Implementing a new command has become an extremely expensive task due to the amount of test files that need to be amended (development time) and the number of teams owning such files (code review time):
jstests/auth/internal_command_auth_validation.js jstests/auth/lib/commands_lib.js jstests/core/catalog/views/views_all_commands.js jstests/libs/write_concern_all_commands.js jstests/replsets/all_commands_downgrading_to_upgraded.js jstests/replsets/db_reads_while_recovering_all_commands.js jstests/sharding/all_commands_direct_shard_connection_auth.js jstests/sharding/database_versioning_all_commands.js jstests/sharding/libs/last_lts_mongod_commands.js jstests/sharding/libs/last_lts_mongos_commands.js jstests/sharding/libs/mongos_api_params_util.js jstests/sharding/read_write_concern_defaults_application.js jstests/sharding/safe_secondary_reads_drop_recreate.js jstests/sharding/safe_secondary_reads_single_migration_suspend_range_deletion.js jstests/sharding/safe_secondary_reads_single_migration_waitForDelete.js
This ticket is to investigate ways to improve this, most probably carrying out an initial assessment and involve other server teams before proposing a final solution.