[SERVER-14239] backport db.upgradeCheck* to 2.4.x shell Created: 12/Jun/14 Updated: 31/Jul/15 Resolved: 05/Aug/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Shell |
| Affects Version/s: | 2.6.2 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Thomas Rueckstiess | Assignee: | Matt Kangas |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | community-team | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Server 2.7.3, Server 2.7.4, Server 2.7.5 |
| Participants: |
| Description |
|
It's confusing and inconvenient for users that they need to install 2.6.x somewhere to gain access to the db.upgradeCheck* helpers. We should backport it to the next 2.4.x shell so that it is already available for users still running on latest 2.4. |
| Comments |
| Comment by Ramon Fernandez Marina [ 05/Aug/14 ] |
|
This backport is not trivial, and is potentially risky. Users have an easy workaround, namely download the 2.6.x MongoDB binaries and from there run the mongo shell to get access to the db.upgradeCheck* helpers. |