[SERVER-32366] Move dropDatabase logic from ShardingCatalogClient into ShardingCatalogManager Created: 15/Dec/17  Updated: 27/Oct/23  Resolved: 16/Jan/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Kaitlin Mahar Assignee: Kaitlin Mahar
Resolution: Gone away Votes: 0
Labels: sharding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-01-01, Sharding 2018-01-15, Sharding 2018-01-29
Participants:

 Description   

The bulk of the dropDatabase business logic currently sits in a function on the ShardingCatalogClient.
As part of moving the dropDatabase command to the config server, we should move the business logic from the ShardingCatalogClient to the ShardingCatalogManager.

Note, the ShardingCatalogClient hierarchy is:
ShardingCatalogClient base class
--> child class ShardingCatalogClientImpl (the real implementation)
--> child class ShardingCatalogClientMock (has dummy methods)
Moving the dropDatabase function will require deleting code from all three of these classes.
Also note, moving the dropDatabase function will also require updating some unit tests.



 Comments   
Comment by Kaitlin Mahar [ 16/Jan/18 ]

Closing this as it turns out none of the dropDatabase logic is in the ShardingCatalogClient - it is all already contained in the _configsvrDropDatabase command - so there is nothing to move.

Generated at Thu Feb 08 04:30:01 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.