[SERVER-17646] Add an upgradeCheck for 3.0 upgrade to validate any breaking changes Created: 18/Mar/15 Updated: 06/Dec/22 Resolved: 14/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics, Usability |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Anil Kumar | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Sharding
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
It would be useful to have an upgradeCheck command similar to one that exists for 2.4 to 2.6 upgrade just for documents. Having an automated way to perform the pre-requisite validations for an upgrade across major versions is a better end-user experience than going through the compatibility list to validate what will break. A few samples from compatibility list that can be incorporated into the upgradeCheck are:
|
| Comments |
| Comment by Gregory McKeon (Inactive) [ 14/Sep/18 ] |
|
We now have featureCompatibilityVersion and haven't heard from Support about this, so closing as gone away. |
| Comment by Sam Kleinman (Inactive) [ 18/Mar/15 ] |
|
scotthernandez, assigning to you for assessment and additional research. |