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

Clean up PlanExecutor interface for SBE

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.7.0
    • None
    • None
    • None
    • Fully Compatible
    • Query 2020-08-24, Query 2020-09-07
    • 0

    Description

      With the introduction of the slot-based execution (SBE) engine, the server will support two completely unrelated query execution engines. Luckily, PlanExecutor, the type which represents a query execution plan, was already an interface. However, some of the interface methods involved details of the pre-existing execution engine. We should narrow the interface so that it only contains methods which make sense for both the slot-based engine and the "classic" engine. For example, PlanExecutor::getRootStage() returns a pointer to a "classic" PlanStage, and therefore does not make sense in the context of SBE.

      Attachments

        Activity

          People

            david.storch@mongodb.com David Storch
            david.storch@mongodb.com David Storch
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: