-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
Sharding NYC 2023-10-30
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"