[SERVER-79874] Explain command returns error when database does not exists Created: 09/Aug/23 Updated: 10/Aug/23 Resolved: 09/Aug/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tommaso Tocci | Assignee: | Backlog - Query Execution |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Execution
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| 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 |