[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:
Depends
is depended on by SERVER-72797 Remove sharding exceptions from inval... Blocked
Duplicate
is duplicated by SERVER-79874 Explain command returns error when da... Closed
is duplicated by SERVER-82095 Make explain command behave the same ... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
SERVER-82052 Unify behavior for explain().find() w... Sub-task Closed Colin Stolley  
SERVER-83547 Unify behavior for explain().aggregat... Sub-task Open Backlog - Query Execution  
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

Generated at Thu Feb 08 06:31:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.