[SERVER-75857] Unify behavior between mongod and mongos when running explain on a nonexistent database Created: 07/Apr/23 Updated: 12/Dec/23 |
|
| Status: | In Progress |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kyle Suarez | Assignee: | Mickey Winters |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | pm3278-m1 | ||
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Issue Links: |
|
||||||||||||||||||||
| Sub-Tasks: |
|
||||||||||||||||||||
| Assigned Teams: |
Query Execution
|
||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
On a mongod, running an explain on a nonexistent database returns a success result with an EOF plan. On a mongos, the same explain will throw an error. The goal of this ticket is to unify the behavior between the two and have a single agreed-upon response. |
| Comments |
| Comment by Mickey Winters [ 07/Dec/23 ] |
|
reassigning to me since I will do the other subtask |