Refactor plan ranking code to allow new planning strategies

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Optimization
    • Fully Compatible
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently plan ranking logic is all sitting in get_executor.cpp in its finishPrepare method and it is switching between multiplanning and CBR using if-else branches. We need to add a few more strategies that would potentially combine multiplanning and CBR together in some form. Pave the way for those new planning strategies by refactoring it into a better OOP design

            Assignee:
            Carlos Alonso Pérez
            Reporter:
            Carlos Alonso Pérez
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: