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

Prototype CBR entry point as a PlannerInterface implementation

    • Type: Icon: Task Task
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Optimization

      In the current plan enumeration/multi-planning architecture CBR can be thought of as an efficient alternative to mutli-planning. Following the approach how multi-planning fits into the query planner architecture, CBR is introduced as an implementation of two variants of mongo::PlannerInterface:

      • classic_runtime_planner::ClassicPlannerInterface
      • classic_runtime_planner_for_sbe::PlannerBase
        CBR is chosen as an alternative to the corresponding MultiPlanner classes.

      The implementation will based on WRITING-25693.

      The functionality is tested via a JS test.

      Unit testing is not used because it would have to instantiate all the environment needed to call getExecutorFind. There is no single existing test that does that.

            Assignee:
            timour.katchaounov@mongodb.com Timour Katchaounov
            Reporter:
            timour.katchaounov@mongodb.com Timour Katchaounov
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: