-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Execution
-
Fully Compatible
-
0
-
None
-
None
-
None
-
None
-
None
-
None
-
None
- sbe_pushdown_replan_reason.js checks for the presence of replanReason on the profile entry for SBE cached queries which went through the replanning process.
- The suite runs FCV upgrade/downgrade commands, which influence the enabled feature flags
- One of those feature flags is featureFlagShardFilteringDistinctScan
color: Color value is invalid
, which will make the query use classic instead of SBE due to distinct multiplanning
color: Color value is invalid
Starting with SERVER-92456 we use classic instead of sbe when
{{featureFlagShardFilteringDistinctScan
color: Color value is invalid
is enabled.
}}
color: Color value is invalid
We should instead only check the presence of the replanReason if the featureFlagShardFilteringDistinctScan is not enable