[SERVER-86280] Reclassify some collection validation warnings/errors Created: 06/Feb/24  Updated: 06/Feb/24

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

Type: Improvement Priority: Major - P3
Reporter: Gregory Noma Assignee: Gregory Noma
Resolution: Unresolved Votes: 0
Labels: storex-shortlist
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Duplicate
is duplicated by SERVER-86204 Document schema validation errors sho... Closed
Backport Requested:
v7.3, v7.0, v6.0
Sprint: Execution Team 2024-03-04
Participants:

 Description   

Collection validation has two classifications for its results: warnings and errors. Typically warnings do not indicate data corruption and errors do indicate data corruption. However, currently there are some validation results which we report as errors despite not indicating real data corruption. A couple examples of this are document schema violations and unrecognized index spec fields. We should consider reclassifying some of these so that they are not reported as data corruption. However, we should make sure we can still catch these cases if they occur in our testing.



 Comments   
Comment by Gregory Noma [ 06/Feb/24 ]

One idea I had is to add a third category to validation results: info. We can move most things currently categorized as warnings down to info, and then we can move some of what is currently categorized as errors down to warnings. Then in our testing we can still fail if there are any validation warnings, but outside of our testing warnings will not be considered data corruption.

Another option is to leave just two categories and simply move some things down from errors to warnings. But, in order to make sure we still catch these in testing, we can promote them back to errors if testing diagnostics are enabled.

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