[SERVER-54518] Change command "type" struct field compatibility checker to check for new non-optional fields Created: 12/Feb/21 Updated: 29/Oct/23 Resolved: 03/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Huayu Ouyang | 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-08 |
| Participants: |
| Description |
|
Checking for incompatible command type changes should match the logic of checking for incompatible command parameter changes. Specifically, if the command type is a struct, if a new non-optional field is added to the struct, it should fail. If an old unstable field in the struct is changed to a stable, non-optional field, it should also fail. |
| Comments |
| Comment by Githook User [ 03/Mar/21 ] |
|
Author: {'name': 'Huayu Ouyang', 'email': 'huayu.ouyang@mongodb.com', 'username': 'huayu-ouyang'}Message: |