Make count command behave the same in replicaset and sharded cluster when db does not exists

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Do
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      On replica-set deployments, a count command with an invalid query sent for a database that doesn't exist will fail (e.g. BadValue )
      On the other hand on sharded cluster same command will work just fine and return no results.

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

              Created:
              Updated:
              Resolved: