[SERVER-84077] Annotate EOF plans with a type field describing why the EOF was created Created: 11/Dec/23 Updated: 25/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: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Optimization
|
||||||||
| Participants: | |||||||||
| Description |
|
CQF 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. It would be convenient to differentiate these cases in the explain output. This ticket is to annotate the EOF stage with a description of why it was created. |