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

XMLWordPrintableJSON

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

      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:
              [DO NOT USE] Backlog - Query Optimization
              Reporter:
              Catalin Sumanaru
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: