The current okForStorage misses some edge cases. For the new update framework, we would like to fix these.
Marking QA needed since an adversary trying to produce bad field names would be helpful.
- is depended on by
-
SERVER-10298 Apply okForStorage to object replacement updates in modifier_object_replace
- Closed
- is duplicated by
-
SERVER-10002 Possible to create docs with dotted field names
- Closed
- related to
-
SERVER-10379 Allow sharding metadata collections to bypass okForStorage checks
- Closed