[SERVER-71163] Remove CQF-specific variant Created: 08/Nov/22  Updated: 20/Jun/23

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

Type: Task Priority: Major - P3
Reporter: Hana Pearlman Assignee: Backlog - Query Optimization
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-67034 Enable 'featureFlagSbeFull' by default Backlog
Related
is related to SERVER-66954 Create new build variant which enable... Closed
is related to SERVER-77815 Expand coverage in the CQF variant an... Closed
Assigned Teams:
Query Optimization
Participants:

 Description   

Currently, the CQF feature flag (featureFlagCommonQueryFramework) is marked as always-disabled, so we don't get CQF coverage by default on the all-feature-flags variants. One reason we wanted to wait on taking the CQF FF off the always-disabled list is that, once enabled, it would take precedence over the SBE feature flag (featureFlagSbeFull), reducing coverage of the SBE stage builders. 

To get some additional coverage, in SERVER-66954 we introduced a new variant with a select list of tasks to run with the CQF feature flag enabled manually. This was intended to be a temporary measure; this ticket tracks deleting the new variant.



 Comments   
Comment by Hana Pearlman [ 08/Nov/22 ]

There is some question about the exact timing of this ticket. Once the SBE FF is enabled by default, in theory we should be able to 1) remove the CQF FF from the always-disabled list and 2) delete the CQF-specific variant. It's possible that 1) is somewhat hard to do, since it will increase the passthrough coverage of the feature flag a lot.

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