-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
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 SERVER-61685 would be blocked).
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
- is depended on by
-
SERVER-61685 Remove isTimeseriesNamespace flag for collMod after 6.0 branching
- Closed
- is related to
-
SERVER-68621 Investigate potentially unintended additions to the stableAPI
- Closed
- related to
-
SERVER-65026 Add a sharded passthrough suite which sets 'apiStrict:true' for all the Stable API commands
- Closed