[SERVER-54854] Stop type checking unstable fields Created: 01/Mar/21 Updated: 29/Oct/23 Resolved: 25/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | IDL |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc0 |
| 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, Repl 2021-04-05 |
| Participants: |
| Description |
|
We make no guarantees for type incompatibility for unstable fields, so we should allow for incompatible changes to unstable fields. The one exception is that we should error if an unstable field is added with a new use of bson_serialization_type "any" without being added to the allowList. This is because unstable fields can be used for experimental fields that ultimately become stable, so we should warn away from using the "any" type as soon as we can. |
| Comments |
| Comment by Githook User [ 25/Mar/21 ] |
|
Author: {'name': 'Huayu Ouyang', 'email': 'huayu.ouyang@mongodb.com', 'username': 'huayu-ouyang'}Message: |