Allow "undefined" BSON type in metaField in the BucketUnpacker

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Execution
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The BucketUnpacker currently has an assertion that the metaField for a bucket is not undefined. However, there is nothing stopping a user from inserting documents into a time-series collection that have undefined for the metaField, or performing an update to change the metaField to undefined. In either of these cases, the user would then be unable to query their time-series collection until these documents are removed.

            Assignee:
            [DO NOT USE] Backlog - Query Execution
            Reporter:
            Gregory Noma
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: