[SERVER-60669] Should we rename internalQueryForceClassicEngine? Created: 13/Oct/21  Updated: 06/Dec/22  Resolved: 14/Oct/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Question Priority: Major - P3
Reporter: Jennifer Peshansky (Inactive) Assignee: Backlog - Query Execution
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Query Execution
Participants:

 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.


Generated at Thu Feb 08 05:50:25 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.