[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: |
|
||||||||||||||||||||
| 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 |
| 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. |