[SERVER-65002] Create a new IDL syntax for internal parameters Created: 28/Mar/22 Updated: 29/Oct/23 Resolved: 01/Aug/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Huayu Ouyang | Assignee: | Rui Liu |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Currently, for some internal parameters that mongos attaches before sending it to the shards, we cannot mark them as unstable in the IDL because the shards will run parsing validation, and see that the command is using an unstable parameter, and show an APIStrictError. However, since marking them as stable makes them a part of the stable API, we will then not be allowed to remove them (i.e. tickets like We should look into creating a new IDL syntax to be able to mark parameters as unstable, but for internal use, and modify the parsing validation so that using these parameters internally with apiStrict: true won't cause an APIStrictError |
| Comments |
| Comment by Huayu Ouyang [ 29/Mar/22 ] |
|
Should also mark runtimeConstants in the update command and runtimeConstants in the findAndModify command as unstable |