[SERVER-2048] Cannot remove _id_ index from capped collection Created: 01/Nov/10 Updated: 06/Dec/22 Resolved: 02/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Fix | Votes: | 7 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
If for some reason you create a {_id:1} index on capped collection, there is no way to remove it. both dropIndex("id") and .dropIndexes() fail > db.testCapped.dropIndex("id") { "nIndexesWas" : 1, "errmsg" : "may not delete _id index", "ok" : 0 }> db.testCapped.dropIndexes() |
| Comments |
| Comment by William Tiu [ 12/Dec/11 ] |
|
After talking to the 10gen guys, was told to add an up vote to this. Since it's been over a year since this ticket has been updated, I figure a comment is warranted as well to possibly up the chances of it getting fixed. |