- ShardSvrProcessInterface::getCollectionOptions() always routes to the primary shard: https://github.com/mongodb/mongo/blob/07e852967e936adbc255518ebaa9c116937becc4/src/mongo/db/pipeline/process_interface/shardsvr_process_interface.cpp#L252-L253. What should the routing behavior be for a listCollections – should we still target the primary shard?
- ShardSvrProcessInterface::getIndexSpecs() always routes to the primary shard: https://github.com/mongodb/mongo/blob/07e852967e936adbc255518ebaa9c116937becc4/src/mongo/db/pipeline/process_interface/shardsvr_process_interface.cpp#L311-L312
- Changes related to renameIfOptionsAndIndexesHaveNotChanged() should be done by
SERVER-79661.
Still need to figure out if anything needs to change for createTimeseriesView(), createIndexesOnEmptyCollection(), and dropCollection().
- causes
-
SERVER-82811 ShardsvrProcessInterface::dropCollection should accept NamespaceNotFound errors due to the database having been dropped
- Closed
- is related to
-
SERVER-79661 Make "internalRenameIfOptionsAndIndexesMatch" command sharding-aware
- Closed