[DOCS-2782] add warning about downgrade implications of text indexes for 2.6 to 2.4 Created: 24/Feb/14 Updated: 26/Feb/14 Resolved: 26/Feb/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.1, mongodb-2.6 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Michael O'Brien | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | sprint-slipstream | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 9 years, 51 weeks, 1 day ago | ||||||||
| Description |
|
"Run a downgrade 2.6 -> 2.4, with a TIV2 index in place. Expected behavior: 2.4.9 should report the issue and fail inserts, since it checks the index version. Prior to 2.4.9 doesn’t check, so it can cause index corruption if language names aren’t just all lowercase in the existing index entries (cause they can’t be removed by 2.4.<9). " We need to document this and strongly warn that only downgrading to 2.4.9 should be done, because if the user downgrades to 2.4.8 or lower they could end up corrupting their index. |
| Comments |
| Comment by Githook User [ 26/Feb/14 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |