[SERVER-54018] Restrict metadata and time fields to top-level fields Created: 25/Jan/21 Updated: 08/Feb/21 Resolved: 08/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Gregory Noma | Assignee: | Dan Larkin-York |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Execution Team 2021-02-08, Execution Team 2021-02-22 |
| Participants: |
| Description |
|
We should restrict the metaField and timeField to be top-level fields in the document schema. In particular, if a "dotted" field name (i.e. "a.b.c") is provided at collection creation, it should be rejected. |
| Comments |
| Comment by Githook User [ 08/Feb/21 ] |
|
Author: {'name': 'Dan Larkin-York', 'email': 'dan.larkin-york@mongodb.com', 'username': 'dhly-etc'}Message: |