-
Type: Bug
-
Resolution: Won't Fix
-
Priority: Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: Index Maintenance
-
Labels:None
-
Storage Execution
-
ALL
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()
{
"nIndexesWas" : 1,
"msg" : "non-_id indexes dropped for collection",
"ok" : 1
}
- related to
-
SERVER-2019 _id index on capped collection : inconsistent between master and slave
- Closed