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

When planning fails because there is no way to answer the query, it should emit ErrorCodes::NoQueryExecutionPlans

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Gone away
    • 3.2.6
    • None
    • Querying
    • None
    • Query

    Description

      The planner now uses ErrorCodes::BadValue when it fails due to the absence of any available query solutions. This is too generic. Instead we should introduce ErrorCodes::NoQuerySolutions in order to allow clients to check for this particular error case.

      Original description

      I'm doing some work trying to get MongoDB 3.2 to work with parse-server. parse-server has a feature where if you do a geo query and don't have the appropriate index, it catches the error, creates the index, then retries the query. Previously this worked by catching the error code 17007 but in MongoDB 3.2 it appears that this error code is now 2.

      I wanted to check if this was expected behavior before coding around the issue.

      Attachments

        Issue Links

          Activity

            People

              backlog-server-query Backlog - Query Team (Inactive)
              tyler.brock@gmail.com Tyler Brock
              Votes:
              1 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: