-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Replication
-
Fully Compatible
-
Repl 2023-04-03, Repl 2023-04-17
We should rename isEnabledAndIgnoreFCV() to be isEnabledAndIgnoreFCVUnsafe() and require any usages to have a comment in some number of lines preceding it. This is because we want to avoid using isEnabledAndIgnoreFCV() in general
For places where commands and aggregation states/expressions are registered that use isEnabledAndIgnoreFCV, we should add a function isEnabledAndIgnoreFCVAtStartup() which has the same behavior as isEnabledAndIgnoreFCVUnsafe() but won’t require a comment.
We should also add better documentation about when to use isEnabled vs isEnabledAndIgnoreFCVAtStartup
- related to
-
SERVER-75389 Confirm FeatureFlag::isEnabledAndIgnoreFCVUnsafe() usage for sharding
- Backlog
-
SERVER-75387 Confirm FeatureFlag::isEnabledAndIgnoreFCVUnsafe() usage for storage execution
- Closed
-
SERVER-75388 Confirm FeatureFlag::isEnabledAndIgnoreFCVUnsafe() usage for query
- Closed
-
SERVER-75396 Confirm FeatureFlag::isEnabledAndIgnoreFCVUnsafe() usage for security
- Closed