Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-84076

Differentiate EOF plans generated because of non-existent namespace vs expression simplification

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Query Optimization

    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.

      Attachments

        Activity

          People

            backlog-query-optimization Backlog - Query Optimization
            hana.pearlman@mongodb.com Hana Pearlman
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated: