[SERVER-8619] Drop of collection or database should drop tag range Created: 19/Feb/13 Updated: 06/Dec/22 Resolved: 20/Feb/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.4.0-rc0 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | James Wahlin | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Sharding
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
Currently when a collection is dropped, associated tag ranges (in the config database tag collection) remain in place. Please change to drop collection specific tag data as well. I would expect drop() to completely remove a collection as well as associated metadata. |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 20/Feb/13 ] |
|
Current behavior is by design. |