@@ -155,35 +155,28 @@ where
155
155
///
156
156
/// To add a new feature flag, do the following steps:
157
157
///
158
- /// 1. To make the flag available to all stages in our [`Optimize`] pipelines:
159
- /// 1. Add the flag as an [`OptimizerConfig`] field.
160
- ///
161
- /// 2. To allow engineers to set a system-wide override for this feature flag:
162
- /// 1. Add the flag to the `feature_flags!(...)` macro call.
163
- /// 2. Extend the `From<&SystemVars>` implementation for [`OptimizerConfig`].
158
+ /// 1. To make the flag available to all stages in our [`Optimize`] pipelines
159
+ /// and allow engineers to set a system-wide override:
160
+ /// 1. Add the flag to the `optimizer_feature_flags!(...)` macro call.
161
+ /// 2. Add the flag to the `feature_flags!(...)` macro call and extend the
162
+ /// `From<&SystemVars>` implementation for [`OptimizerFeatures`].
164
163
///
165
- /// 3 . To enable `EXPLAIN ... WITH(...)` overrides which will allow engineers to
164
+ /// 2 . To enable `EXPLAIN ... WITH(...)` overrides which will allow engineers to
166
165
/// inspect plan differences before deploying the optimizer changes:
167
- /// 1. Add the flag as a [`mz_repr::explain::ExplainConfig`] field.
168
- /// 2. Add the flag to the `ExplainPlanOptionName` definition.
169
- /// 3. Add the flag to the `generate_extracted_config!(ExplainPlanOption,
166
+ /// 1. Add the flag to the `ExplainPlanOptionName` definition.
167
+ /// 2. Add the flag to the `generate_extracted_config!(ExplainPlanOption,
170
168
/// ...)` macro call.
171
- /// 4 . Extend the `TryFrom<ExplainPlanOptionExtracted>` implementation for
169
+ /// 3 . Extend the `TryFrom<ExplainPlanOptionExtracted>` implementation for
172
170
/// [`mz_repr::explain::ExplainConfig`].
173
- /// 5. Extend the `OverrideFrom<ExplainContext>` implementation for
174
- /// [`OptimizerConfig`].
175
171
///
176
- /// 4 . To enable `CLUSTER ... FEATURES(...)` overrides which will allow
172
+ /// 3 . To enable `CLUSTER ... FEATURES(...)` overrides which will allow
177
173
/// engineers to experiment with runtime differences before deploying the
178
174
/// optimizer changes:
179
- /// 1. Add the flag to the `optimizer_feature_flags!(...)` macro call.
180
- /// 2. Add the flag to the `ClusterFeatureName` definition.
181
- /// 3. Add the flag to the `generate_extracted_config!(ClusterFeature, ...)`
175
+ /// 1. Add the flag to the `ClusterFeatureName` definition.
176
+ /// 2. Add the flag to the `generate_extracted_config!(ClusterFeature, ...)`
182
177
/// macro call.
183
- /// 4 . Extend the `let optimizer_feature_overrides = ...` call in
178
+ /// 3 . Extend the `let optimizer_feature_overrides = ...` call in
184
179
/// `plan_create_cluster`.
185
- /// 4. Extend the `OverrideFrom<OptimizerFeatureOverrides>` implementation
186
- /// for [`OptimizerConfig`].
187
180
#[ derive( Clone , Debug ) ]
188
181
pub struct OptimizerConfig {
189
182
/// The mode in which the optimizer runs.
0 commit comments