[SERVER-69163] Enforce Schema on System Collections Created: 25/Aug/22  Updated: 05/Dec/22  Resolved: 15/Nov/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Matt Panton Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Duplicate Votes: 0
Labels: shardingemea-qw
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-39122 Enforce schema on system collections Closed
Related
is related to SERVER-39122 Enforce schema on system collections Closed
is related to SERVER-68852 Investigate handling of incorrect val... Closed
Assigned Teams:
Sharding EMEA
Participants:
Story Points: 1.33

 Description   

Enforce Schema on System Collections:

It was recently discovered that, for years, the documentation had an incorrect example for a write concern document for _secondaryThrottle affecting who knows how many users. It could be avoided if we enforce schema validation on the system collections. There are several other fields that could benefit from schema validation.

It can be incremental (non-strict) aka done in phases



 Comments   
Comment by Garaudy Etienne [ 02/Sep/22 ]

since we said it can be done in phases, I suggest a quick win and letting the system do its thing. The only early work needed is defining the list of items on there and ranking them. That way we can compare each individual field/document with the rest of the quick wins instead of all the system collections.

Comment by Cris Insignares Cuello [ 02/Sep/22 ]

tommaso.tocci@mongodb.com if I understood correctly this ticket has significant work (3-4 weeks for an engineer). am I correct? garaudy.etienne@mongodb.comjust to clarify then it was decided this will be done by EMEA, if we add it as a qw we cant commit to a timeline due to the capacity constraints.

Comment by Garaudy Etienne [ 01/Sep/22 ]

It's a P4, so just put it in the quick wins bucket. do we need a new server ticket for each field?

Comment by Cris Insignares Cuello [ 01/Sep/22 ]

garaudy.etienne@mongodb.com/matt.panton@mongodb.com it was decided then that this will be done by EMEA? Due to the time constraints when should we schedule this work?

Generated at Thu Feb 08 06:12:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.