-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
Cluster Scalability 2023-12-25
- depends on
-
SERVER-84264 Make DBClientBase for the shell never uassert StaleConfig internally
-
- Closed
-
-
SERVER-84265 Make jscore tests that currently expect mongod explain format handle mongos explain format
-
- Closed
-
- related to
-
SERVER-84342 listCollections command doesn't return collections created directly through applyOps commands
-
- Open
-
-
SERVER-84091 cloneCollectionAsCapped command stops working after a replica set is bootstrapped as a sharded cluster
-
- Closed
-
-
SERVER-84331 createCollection command for capped collections on sharded cluster requires the "size" field but the same command on replica set it doesn't
-
- Closed
-
-
SERVER-84263 ServiceEntryPointCommon in test mode may try to verify contract for a command before clearing access and privilege checks from the previous command in the same auth session
-
- Closed
-
-
SERVER-84329 renameCollection command targeting a valid, existing collection fails on a sharded cluster, but succeeds on a replica set in the presence of invalid views
-
- Closed
-
-
SERVER-84330 renameCollection on sharded cluster fails if the destination database doesn't exist but doesn't fail on replica set
-
- Closed
-
-
SERVER-84332 Add jscore passthrough testing for connecting to a single-shard cluster using replica set endpoint
-
- Closed
-
-
SERVER-84349 Remove dbhash2.js
-
- Closed
-
-
SERVER-84362 Investigate ObjectIsBusy error in the replica set endpoint suite when the ValidateCollections hook is enabled
-
- Closed
-
-
SERVER-86836 disable ValidateCollections hook in replica set endpoint tests
-
- Closed
-
-
SERVER-84307 find command against non-existent collection on sharded cluster doesn't show up in response to top command but the same command on replica set does
-
- Needs Scheduling
-