-
Type:
Task
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
Sharding
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Right now most of the implementation of sharded dropDatabase functionality is in DBConfig::dropDatabase, which cannot be easily unit tested. This functionality logically belongs to the catalog manager, and also would be able to be unit tested if that was where it lived.