Explain command returns error when database does not exists

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In sharded clusters, the explain command return a NamespaceNotFound error when the database doesn't exist. On the other hand on plain replicaset/standalone deployments the explain command return ok:1 when database doesn't exists.

      The goal of this ticket is to change the behavior of explain command in sharded cluster such that it won't return any error when the database doesn't exist

              Assignee:
              [DO NOT USE] Backlog - Query Execution
              Reporter:
              Tommaso Tocci
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: