[SERVER-82390] Update IDL strict field for move/unshardCollection Created: 23/Oct/23 Updated: 25/Oct/23 Resolved: 25/Oct/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kruti Shah | Assignee: | Kruti Shah |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding NYC 2023-10-30 |
| Participants: |
| Description |
|
Copying over Max's message: moveCollection and unshardCollection using "strict:false" would imply that unknown/misspelled arguments to mongos won't cause the client/operator to see an error. While "strict:false" is helpful for internal commands to allow greater flexibility around mixed version clusters / upgrade, the public facing commands should still be "strict:true" |
| Comments |
| Comment by Githook User [ 25/Oct/23 ] |
|
Author: {'name': 'Kruti Shah', 'email': 'kruti.shah@mongodb.com', 'username': 'krutishah139'}Message: |