[SERVER-3589] server downgrade doesn't handle new index version Created: 12/Aug/11 Updated: 11/Jul/16 Resolved: 17/Aug/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | 1.9.1 |
| Fix Version/s: | 1.8.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Chris Westin | Assignee: | Eliot Horowitz (Inactive) |
| 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 |
|
The docs and qa bug indicate that a downgrade should fail, or that at least operations against a newer index format should fail: Create a collection with an index on it and verify new index version format: db = db.getSisterDB("qadb"); db.idx1.drop(); ); ); var idxlist = db.idx1.getIndexes(); downloaded 1.8.2. start it on the same database files. mongod starts up normally. > use qadb > db.idx1.find( {b:1}); { "_id" : ObjectId("4e445314fb3e65e39a74d26c"), "a" : 1, "b" : 1 }> db.idx1.find( {a:1}); , , |
| Comments |
| Comment by auto [ 17/Aug/11 ] |
|
Author: {u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: better handling of new index versions |