[SERVER-52925] Ban incompatible validator changes in API Version 1 IDL command definitions Created: 18/Nov/20 Updated: 29/Oct/23 Resolved: 25/Feb/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: | A. Jesse Jiryu Davis | 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 | ||||||||
| Participants: | |||||||||
| Description |
|
A few API Version 1 commands accept parameters that have validators defined in IDL. For example, "listCollections" accepts {cursor: {batchSize: x}}, where "x" is an integer with a validator that checks it is non-negative. As part of our IDL compatibility checking, implement the simplest possible rules for validators. |
| Comments |
| Comment by Githook User [ 25/Feb/21 ] |
|
Author: {'name': 'Huayu Ouyang', 'email': 'huayu.ouyang@mongodb.com', 'username': 'huayu-ouyang'}Message: |