Unify find behavior between mongod and mongos when running explain on a nonexistent database

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • Fully Compatible
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      On a mongod, running an explain on a nonexistent database returns a success result with an EOF plan. On a mongos, the same explain will throw an error.

      The goal of this ticket is to unify the behavior between the two and have a single agreed-upon response.

            Assignee:
            Mickey Winters
            Reporter:
            Kyle Suarez (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: