[SERVER-54855] Allow unstable fields to become stable if they are optional or have a default Created: 01/Mar/21 Updated: 29/Oct/23 Resolved: 18/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | IDL |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Samyukta Lanka | Assignee: | Huayu Ouyang |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Repl 2021-03-22 |
| Participants: |
| Description |
|
When making an unstable field stable, we only allow it to be optional in the new version. However, it would still be compatible to make the field required but have a default (since this will not break existing command requests). |
| Comments |
| Comment by Githook User [ 18/Mar/21 ] |
|
Author: {'name': 'Huayu Ouyang', 'email': 'huayu.ouyang@mongodb.com', 'username': 'huayu-ouyang'}Message: |