[SERVER-32350] Don't skip storage validation for updates to config documents Created: 14/Dec/17 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Justin Seyster | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | mql-semantics | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Execution
|
| Participants: |
| Description |
|
One of the criteria used here to decide when to skip storage_validation::storageValid() is the isConfigDB() namespace property. Previously, we had to skip this check, because storage validation would reject fields with a "." in them, which are sometimes necessary in the config database. That check has been removed from storage validation, however, so we should be clear to validate config documents. |