Recategorize BSON validation checks by severity

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Storage Execution 2025-10-27
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently the non-default BSON validation checks are roughly grouped by cost. This approach makes the collection validation output to be noisy with trivial issues like deprecated BSON types. Recategorizing them by severity will help because more serious errors are expected to be less common.

            Assignee:
            Benjamin Pearce
            Reporter:
            Yuhong Zhang
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: