Revisit if PrepareExecutionHelper should be exposing internal engine choice

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

      Based on feedback from the PR from SERVER-117697

      I think this is okay for now but I would like to revisit whether PrepareExecutionHelper and its instances should really be exposing internal engine choice and how to design around it. It feels like an abstraction leakage since previously, the callers wouldn't know the specifics of the engine type and could treat instances of PrepareExecutionHelper uniformly. Ideally, we are able to make the new plan ranking code templated/more engine agnostic in the future to avoid needing this. I don't think we need a ticket per-se but more of a point to bring up in future discussions around refactoring in this area of code.

            Assignee:
            Unassigned
            Reporter:
            Peter Volk
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: