[SERVER-42709] Change error message about missing UUIDs on startup Created: 08/Aug/19 Updated: 29/Oct/23 Resolved: 13/Aug/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 4.0.11 |
| Fix Version/s: | 4.0.13 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Xiangyu Yao (Inactive) | Assignee: | Xiangyu Yao (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Execution Team 2019-08-12, Execution Team 2019-08-26 | ||||
| Participants: | |||||
| Description |
|
On 4.0, when we detect a collection is missing UUID on startup, we give a MustDowngrade error because starting from 3.6, all collections should have UUID. But this error message does not give enough information about which collection was missing UUID and how to deal with this issue. |
| Comments |
| Comment by Githook User [ 15/Aug/19 ] |
|
Author: {'email': 'ben.caimano@10gen.com', 'name': 'Ben Caimano'}Message: |
| Comment by Githook User [ 13/Aug/19 ] |
|
Author: {'name': 'Xiangyu Yao', 'email': 'xiangyu.yao@mongodb.com', 'username': 'xy24'}Message: |