Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-8168

Better message when accessing a BSON object field that does not exist

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: 2.3.2
    • Component/s: Diagnostics
    • None
    • Fully Compatible
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, it displays:

      assertion: 13111 field not found, expected type <n>

      where <n> is the BSON type. It would be nice if the error would also print out the field name to make debugging much easier.

            Assignee:
            backlog-server-platform DO NOT USE - Backlog - Platform Team
            Reporter:
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: