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

Investigate why empty planner parameters are sometimes used in analyzeDataAccess() calls.

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Optimization

      At the time of writing, there are two call sites for the `analyzeDataAcess()` free function which supply empty `QueryPlannerParameters` instead of the readily available initialised ones:

      • get_executor.cpp::createDistinctSolution() [Line - uses empty parameters for analyzeDataAccess()
        {} query_planner.cpp::QueryPlanner:plan() > buildWholeIXSoln() {*}[Line{} - uses empty parameters for {}buildWholeIXSoln(), which then calls {}analyzeDataAccess(){*}.
      • Consider passing the initialised parameters to the mentioned call-sites.
      • Consider refactoring analyzeDataAccess() to either:
            * Take in optional planner parameters, if they are truly not needed.
            * Re-write analyzeDataAccess() as a more modular interface.

            Assignee:
            backlog-query-optimization [DO NOT USE] Backlog - Query Optimization
            Reporter:
            catalin.sumanaru@mongodb.com Catalin Sumanaru
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: