[SERVER-55398] Dropping a database should also drop all its associated tags Created: 22/Mar/21 Updated: 29/Oct/23 Resolved: 28/Dec/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | Backlog |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Tommaso Tocci | Assignee: | Pol Pinol |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | shardingemea-qw | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Sharding EMEA 2022-12-12, Sharding EMEA 2022-12-26 | ||||||||
| Participants: | |||||||||
| Story Points: | 1.5 | ||||||||
| Description |
|
Currently when dropping a database on sharded cluster we only clean the tags associated with its existing sharded collection but we don't remove any tags associated with unexisting or unsharded collection under it. |
| Comments |
| Comment by Githook User [ 28/Dec/22 ] |
|
Author: {'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}Message: |
| Comment by Githook User [ 21/Dec/22 ] |
|
Author: {'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}Message: Revert " This reverts commit fd2dd311397aa3671e69ae4e4d98056e8006620f. |
| Comment by Githook User [ 19/Dec/22 ] |
|
Author: {'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}Message: |