Not all exceptions inside collection validation should result in {valid: false}

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Storage Execution
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The entire collection validation code block is wrapped inside of a `try catch` block.
      Inside the `try block`, we treat all exceptions as a validation failure. But that isn't always the case. An exception can be thrown if we can't open a checkpoint cursor, if we're trying to open a checkpoint cursor while WiredTiger is running with LSM, etc. These shouldn't be treated as data corrupting failures.

            Assignee:
            [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            Gregory Wlodarek
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: