[SERVER-82107] Make find command behave the same in replicaset and sharded cluster when db does not exists Created: 12/Oct/23 Updated: 05/Feb/24 |
|
| Status: | Backlog |
| 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: | Unresolved | Votes: | 0 |
| Labels: | pm3278-m1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Execution
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
On replica-set deployments, a find command with an invalid namespace sent on a database that doesn't exist will fail with InvalidNamespace. On the other hand on sharded cluster same command will work just fine and return no results.
Additionally |