[SERVER-17425] Disallow creation of v0 indexes Created: 02/Mar/15 Updated: 22/Mar/17 Resolved: 22/Sep/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance, Storage |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.9 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Daniel Pasette (Inactive) | Assignee: | Daniel Pasette (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Minor Change | ||||||||||||||||||||
| Sprint: | QuInt 8 08/28/15, Quint 9 09/18/15, QuInt A (10/12/15) | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Continue process of completing removing v0 indexes, which have been deprecated since v2.0. v0 indexes are already forbidden completely in v3.0 for non-mmap storage engine users. It is currently possible to create new v0 indexes by explicitly passing v:0 into ensureIndex. However, if a new replica set member is brought up, it will be converted to v:1 during initial sync. This ticket captures work to completely disallow explicit creation of v:0 indexes. |
| Comments |
| Comment by Githook User [ 25/Sep/15 ] |
|
Author: {u'username': u'monkey101', u'name': u'Dan Pasette', u'email': u'dan@10gen.com'}Message: |
| Comment by Daniel Pasette (Inactive) [ 22/Sep/15 ] |
|
This requires a dochub endpoint to explain to users how to upgrade their index version and needs to be mentioned in the release notes. |
| Comment by Githook User [ 22/Sep/15 ] |
|
Author: {u'username': u'monkey101', u'name': u'Dan Pasette', u'email': u'dan@10gen.com'}Message: |