[SERVER-3590] v1 indexes don't report their _id in getIndexes() Created: 12/Aug/11 Updated: 29/Aug/11 Resolved: 19/Aug/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | 1.9.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Chris Westin | Assignee: | Dwight Merriman |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Tested on vista 64 |
||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
Following on from the test statements executed at the top of With the downgraded mongod (as per 3589, downgraded from 1.9.3 to 1.8.2), I created another index on the idx1 collection. Then I used getIndexes() to see what I have: > db.idx1.ensureIndex( {b:1}); , , , The b_1 index created with the older server reports an _id, which the newer v:1 indexes do not. This seems like an incorrect non-backwards compatible change – the newer indexes should still have _ids. |