Details
-
Bug
-
Resolution: Duplicate
-
Major - P3
-
None
-
None
-
None
-
None
-
Query Execution
-
ALL
Description
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
Attachments
Issue Links
- duplicates
-
SERVER-75857 Unify behavior between mongod and mongos when running explain on a nonexistent database
-
- In Progress
-