[SERVER-39122] Enforce schema on system collections Created: 22/Jan/19 Updated: 12/Dec/23 Resolved: 04/Dec/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Usability |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Minor - P4 |
| Reporter: | Mark Baker-Munton | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Won't Do | Votes: | 1 |
| Labels: | ShardingRoughEdges, sharding-emea-pm-config-server | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||||||||||
| Story Points: | 3 | ||||||||||||||||||||||||||||
| Description |
|
Enforce schema on system collections to prevent erroneous configurations being allowed. Specifically, the _secondaryThrottle field in the config.settings collection was set incorrectly due to DOCS-11936. If the schema was enforced, the erroneous config could have been prevented. |
| Comments |
| Comment by Mark Baker-Munton [ 06/Feb/19 ] |
|
asya fundamentally the same request as SERVER-25446 just extending out the schema validation functionality to include the config.settings collection (and possibly other system collections). |
| Comment by Asya Kamsky [ 06/Feb/19 ] |
|
mark.baker-munton is this ticket fundamentally same as SERVER-25446? In either case, I'm re-assigning it to the sharding team to triage as these system collections belong to them. |