[SERVER-10309] Mongo should not allow removal of shard key index when the collection is not empty Created: 24/Jul/13 Updated: 06/Dec/22 Resolved: 21/Nov/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.4.0 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Remon van Vliet | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
All |
||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Participants: | |||||||||
| Description |
|
Currently it is allowed to manually remove the shard key index, even if the collection is not empty. I cannot think of a situation where this is desirable and since I think it should reject removal of this index if the collection is sharded. In other words, the only way to remove the shard key collection is to drop the collection. |
| Comments |
| Comment by Asya Kamsky [ 21/Nov/15 ] |
|
dup of |