-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Summary
SERVER-99351 introduced a new API for the FCV-gated feature flags that checks them against the operation FCV.
To ease the transition, existing feature flag checks were allowed to keep using the old API (specified by fcv_context_unaware: true idl parameter).
This ticket is for converting the featureFlagReshardingCloneNoRefresh to use the operation FCV-aware checks.
Background
The featureFlagReshardingCloneNoRefresh is currently checked as part of a phase on the resharding coordinator and the resharding recipient service.
Neither of those cases (1, 2) propagate the operation context to the layer where featureFlagReshardingCloneNoRefresh is checked.
Goal
The goal of this ticket is to:
- Switch featureFlagReshardingCloneNoRefresh to use the new FCVGatedFeatureFlag API by removing the fcv_context_unaware parameter from its idl specification.
- Explore ways to make checking featureFlagReshardingCloneNoRefresh aware of the operation FCV by passing the VersionContext.
Note that the relience on the version context during checks can be bypassed by using one of the dummy values.
This approach will make the feature flag check fallback on the fcv snapshot parameter.
Please use this strategy only when strictly needed, as it might introduce inconsistent behavior if used incorrectly.
- related to
-
SERVER-99351 Incorporate Operation FCV into the FCVGatedFeatureFlag API
-
- Closed
-