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

Improve bison error messages for missing named arguments

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Query Optimization

    Description

      When an argument to an operator is missing, the error message is slightly misleading. As an example, for input {pipeline: [{}]} we get the following error:

      "syntax error, unexpected end of object at element 'end object' "
      "within array at index 0 of input pipeline"

      Would be great to detect the expected token or special case this scenario.

      Attachments

        Activity

          People

            backlog-query-optimization Backlog - Query Optimization
            nicholas.zolnierz@mongodb.com Nicholas Zolnierz
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: