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

Should we rename internalQueryForceClassicEngine?

    XMLWordPrintableJSON

Details

    • Icon: Question Question
    • Resolution: Won't Do
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Query Execution

    Description

      We plan to expose the internalQueryForceClassicEngine setParameter to users in our documentation, which raises the question: should it be called internal?

      Although we have told individual users about internal query knobs before, we have never actually exposed them in the docs. This parameter will be documented and also will likely be around for a long time, so it makes sense to reach a team consensus on the name. We could consider forceClassicEngine or forceClassicQueryEngine, or even going back to enableSlotBasedExecutionEngine.

      Note that name changes cause confusion internally, so if we do decide to change it, we should do so as soon as possible, and I believe we should backport that change to v5.1 as well.

      Attachments

        Activity

          People

            backlog-query-execution Backlog - Query Execution
            jennifer.peshansky@mongodb.com Jennifer Peshansky (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: