-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Query Optimization
-
Fully Compatible
-
QO 2024-04-15, QO 2024-04-29, QO 2024-05-13, QO 2024-05-27, QO 2024-06-10, QO 2024-06-24
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.
- is depended on by
-
COMPASS-8028 Investigate changes in SERVER-84076: Differentiate EOF plans generated because of non-existent namespace vs expression simplification
-
- Closed
-
- is related to
-
-
- Backlog
-