[SERVER-43810] Check if openDB still throws a MustDowngrade error Created: 03/Oct/19 Updated: 29/Oct/23 Resolved: 22/Oct/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.2.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Haley Connelly | Assignee: | Gabriel Marks |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Execution Team 2021-11-01 |
| Participants: |
| Description |
|
Potentially, there may be an extraneous catch case that can be removed. Motivation: From a brief inspection, this seems to no longer be the case for openDB. Instead, it seem like repairCollections calls repairRecordStore which then calls _initCollection, where a MustDowngrade Error can occur. |
| Comments |
| Comment by Githook User [ 22/Oct/21 ] |
|
Author: {'name': 'Gabriel Marks', 'email': 'gabriel.marks@mongodb.com', 'username': 'marksg07'}Message: |