-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: 8.1.0-rc0
-
Component/s: Upgrade/Downgrade
-
None
-
Catalog and Routing
-
Fully Compatible
-
CAR Team 2025-02-03, CAR Team 2025-02-17
A stub to represent FCV independent feature flags (FeatureFlagBinaryCompatible) has been added in SERVER-99281.
The goal of this ticket is to refactor its implementation to only support checks that are expected with feature flags that are not FCV gated e.g. bool FeatureFlagBinaryCompatible::isReleased().
As part of the changes, this ticket should provide a solution for users that can currently accept both FCV-gated and binary-compatible feature flags (for example: server parameters, aggregation stages, ...).
- has to be done after
-
SERVER-99281 Use separate types for FCV-gated vs. non-FCV-gated feature flags
-
- Closed
-
- is depended on by
-
SERVER-99874 Refactor all usages of binary-compatible feature flags to call isEnabled()
-
- Closed
-
- is related to
-
SERVER-77838 Consider changing or removing shouldBeFCVGated parameter
-
- Open
-
-
SERVER-99351 Incorporate Operation FCV into the FCVGatedFeatureFlag API
-
- In Code Review
-
- related to
-
SERVER-100622 Complete TODO listed in SERVER-99302
-
- Blocked
-
-
SERVER-100544 Complete TODO listed in SERVER-99302
-
- Closed
-