[SERVER-30744] Move dropCollection logic from ShardingCatalogClient into ShardingCatalogManager Created: 18/Aug/17 Updated: 30/Oct/23 Resolved: 17/Jan/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.2 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Joanna Huang | Assignee: | Kaitlin Mahar |
| Resolution: | Fixed | 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 2017-12-18, Sharding 2018-01-29 |
| Participants: |
| Description |
|
The bulk of the dropCollection business logic currently sits in a function on the ShardingCatalogClient. As part of moving the dropCollection command to the config server, we should move the business logic from the ShardingCatalogClient to the ShardingCatalogManager. Note, the ShardingCatalogClient hierarchy is: Moving the dropCollection function will require deleting code from all three of these classes. Also note, moving the dropCollection function will also require updating some unit tests. |
| Comments |
| Comment by Githook User [ 17/Jan/18 ] |
|
Author: {'name': 'Kaitlin Mahar', 'email': 'kaitlin.mahar@mongodb.com', 'username': 'kmahar'}Message: |