[SERVER-57770] Consider changing the parameter name internalQueryForceClassicEngine Created: 16/Jun/21  Updated: 27/Oct/23  Resolved: 17/Jun/21

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

Type: Task Priority: Minor - P4
Reporter: Jason Price Assignee: Backlog - Query Execution
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-57758 Turn SBE off by default and invert th... Closed
Assigned Teams:
Query Execution
Participants:

 Description   

Please consider changing this parameter name:

internalQueryForceClassicEngine

Typically, for parameters that would be used externally by customers and documented in our customer facing documentation, we would not document parameters that have "internal" in their name.

Some ideas for consideration by the server team include:

  1. Naming it:

    queryForceClassicEngine

    and keep the Boolean meaning the same.

  2. Even better, naming it:

    enableEnhancedQueryExecution

    and default it to true to enable (false to disable).



 Comments   
Comment by Kyle Suarez [ 17/Jun/21 ]

ger.hartnett, jason.price et al., we are turning SBE off by default in SERVER-57758 and re-enabling it at a later date. The sense of the parameter has inverted, and now its use is to enable SBE rather than disabling it. In that ticket we've chosen internalQueryEnableSlotBasedExecutionEngine as the name.

Let me know how you feel about that name, and if you think it would be best named something else, we can convert this ticket into a different request and send that to the triage queue for discussion.

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