[SERVER-68790] Fix multiversion tests which rely on the renamed internalQueryFrameworkControl knob Created: 12/Aug/22  Updated: 29/Oct/23  Resolved: 12/Sep/22

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

Type: Bug Priority: Major - P3
Reporter: Nicholas Zolnierz Assignee: Nicholas Zolnierz
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:
Linked BF Score: 30

 Description   

Intentionally did not include a method for fixing it, but we renamed the internalQueryForceClassicEngine flag and now the older versions don't recognize the new parameter. The simplest "fix" would be to avoid running multiversion suites in the force-classic-engine variant, but we'd lose a ton of coverage. The better option would be to somehow use this helper to unset the new knob but then also reset to use the old name.



 Comments   
Comment by Githook User [ 09/Sep/22 ]

Author:

{'name': 'Nicholas Zolnierz', 'email': 'nicholas.zolnierz@mongodb.com', 'username': 'nzolnierzmdb'}

Message: SERVER-68790 Avoid setting internalQueryFrameworkControl on 6.0
Branch: v6.0
https://github.com/mongodb/mongo/commit/a8f941b736a6c19e3e39d7822207839bb7e512bb

Generated at Thu Feb 08 06:11:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.