[SERVER-59106] Remove uassert for when newlyAdded field exists in setFeatureCompatibilityVersion Created: 04/Aug/21 Updated: 11/Aug/21 Resolved: 11/Aug/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Vishnu Kaushik | Assignee: | Wenbin Zhu |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Sprint: | Repl 2021-08-23 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Linked BF Score: | 17 | ||||||||||||||||||||||||
| Description |
|
FCV 4.4 doesn't know what the newlyAdded field is, and so we have code to make sure that the newlyAdded field doesn't exist in the config when trying to set the FCV. (Introduced in Now, since we are on 5.1, we can only downgrade to 5.0, and that code can be removed. This ticket is similar: |
| Comments |
| Comment by Vishnu Kaushik [ 04/Aug/21 ] |