[DOCS-15349] [SERVER] Investigate changes in SERVER-66551: Use previous parameter name for controlling query engine Created: 19/May/22  Updated: 13/Nov/23  Resolved: 29/Jun/22

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 6.1.0-rc0, 6.0.0-rc7, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Ian Fogelman
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-66551 Use previous parameter name for contr... Closed
Related
related to DOCS-15339 Investigate changes in SERVER-66445: ... Closed
is related to DOCS-15367 Investigate changes in SERVER-66583: ... Closed
Participants:
Days since reply: 1 year, 37 weeks, 6 days ago
Epic Link: DOCSP-21764

 Description   
Original Downstream Change Summary

This commit makes it such that the parameter to configure SBE is now named 'internalQueryForceClassicEngine' instead of 'internalQueryEnableSlotBasedExecutionEngine'. This is for backwards compatibility versions before 6.0 and after 5.1.

Description of Linked Ticket

As it was made available via Rapid Releases, please continue to use the internalQueryForceClassicEngine parameter name for 6.0+.  Per SERVER-66445, the new default value of this parameter should be true.



 Comments   
Comment by Education Bot [ 19/May/22 ]

Fix Version updated for upstream SERVER-66551:
6.1.0-rc0, 6.0.0-rc7

Comment by Education Bot [ 19/May/22 ]

Fix Version updated for upstream SERVER-66551:
6.1.0-rc0

Generated at Thu Feb 08 08:12:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.