[SERVER-84076] Differentiate EOF plans generated because of non-existent namespace vs expression simplification Created: 11/Dec/23  Updated: 23/Jan/24

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Hana Pearlman Assignee: Backlog - Query Optimization
Resolution: Unresolved Votes: 0
Labels: quick-tech-debt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-84077 Annotate EOF plans with a type field ... Backlog
Assigned Teams:
Query Optimization
Participants:

 Description   

The classic optimizer can create EOF plans for (at least?) two reasons: when the namespace doesn't exist and when expression simplification shows the query will not match any documents. I believe the second one is new as of SERVER-81863. It would be convenient to differentiate these cases in the explain output. For CQF, we will annotate the EOF stage with a description of why it was created. This ticket is to consider the same in classic.


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