Remove BSONColumn content validation from kDefault in BSON validator

ExportXMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Storage Execution 2026-09-28
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      As per this slack thread, we agreed that moving validation of BSONColumn needs to be when parsing the BinData and creating the BSONColumn object, and in the read/write path.

      Context: Today the BSONColumn are validated when validating a BSON object for structural issue. This has been categorized as misplaced because a valid BSON object is still valid even if it contains unparseable BSONColumn as BSONColumn is a BinData format.

            Assignee:
            Binh Vo
            Reporter:
            Guillaume Racicot
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: