[SERVER-19290] move dropDatabase implementation into the catalog manager and add unit tests Created: 06/Jul/15 Updated: 06/Dec/22 Resolved: 09/Jun/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | catalogmetadatacache | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding
|
| Participants: |
| Description |
|
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. |
| Comments |
| Comment by Andy Schwerin [ 09/Jun/16 ] |
|
We'll cover this work when we move all the catalog management behaviors to the config server primary. |