[SERVER-54853] Allow bson_serialization_type "any" in API V1 request/reply fields Created: 01/Mar/21 Updated: 29/Oct/23 Resolved: 08/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 | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Repl 2021-03-08, Repl 2021-03-22 | ||||||||
| Participants: | |||||||||
| Description |
|
We currently disallow a command's request parameter or reply field to have bson_serialization_type "any" because we cannot provide guarantees for its type compatibility for the stable API. However, there are still a lot of valid uses for bson_serialization_type "any", so we do need to support it and do basic compatibility checking for it. We should have an allowList that determines which types can have the "any" type, so that any new usage is only intentionally added. |
| Comments |
| Comment by Githook User [ 08/Mar/21 ] |
|
Author: {'name': 'Huayu Ouyang', 'email': 'huayu.ouyang@mongodb.com', 'username': 'huayu-ouyang'}Message: |