[DOCS-3395] upgradeCheck() docs do not mention what to do about the v:0 warning Created: 12/May/14 Updated: 16/Mar/15 Resolved: 22/Jul/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.8 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Matt Dannenberg | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 9 years, 30 weeks, 1 day ago |
| Description |
|
we should either tell users it's safe to ignore or tell them how to upgrade their indexes via reindex() or both probably best to tell them about reindex since the upgradeChecker cannot check index key constraints for v:0 indexes |
| Comments |
| Comment by Githook User [ 22/Jul/14 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |