[SERVER-30892] MongoDB 3.4 error when failing to start because of a $jsonSchema validator should guide user to upgrade Created: 30/Aug/17 Updated: 06/Dec/22 Resolved: 19/Sep/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Justin Seyster | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query
|
| Participants: |
| Description |
|
If a user tries to start a 3.4 mongod instance, but the database contains a collection that has a $jsonSchema validator, the error message looks like this:
Not terrible, but it would be nice if there were a MustUpgrade error code and a message indicating that $jsonSchema validators require MongoDB 3.6. |
| Comments |
| Comment by David Storch [ 19/Sep/17 ] |
|
It's not looking like we will have time to implement this change, so I'm closing as Won't Fix. In order to ensure the user experience is still good, we should be careful to document the upgrade/downgrade considerations surrounding $jsonSchema validators. |