[SERVER-5667] convertToCapped drops all indexes Created: 20/Apr/12 Updated: 15/Aug/12 Resolved: 20/Apr/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.0.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Jeff lee | Assignee: | Scott Hernandez (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux |
||
| Operating System: | ALL |
| Participants: |
| Description |
|
Hi, It looks like convertToCapped doesn't recreate indexes on the collection. I'm not sure whether or not it's intended behavior but if it's not a bug it would be nice if the documentation could be updated to reflect the need to recreate indexes. Thanks. Steps to replicate: U:Jeffs-MacBook-Air.local> db.foodle.save( { id:1, ts:new Date()}) ) , ) { "ok" : 1 }U:Jeffs-MacBook-Air.local> db.foodle.stats() }, |
| Comments |
| Comment by auto [ 07/Jun/12 ] |
|
Author: {u'login': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by Scott Hernandez (Inactive) [ 20/Apr/12 ] |
|
Yes, that is by design. I will update the docs to make it clear. |