-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: 7.1.0-rc0
-
Component/s: None
-
None
-
Fully Compatible
-
ALL
-
153
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
Fix for BF-28626.
jstests/sharding/query/views.js needs some of its explain output checks updated now that SBE supports clustered collection (CC) scans (from SERVER-74521 delivery on 2023-05-01). This test runs on non-clustered collections unless the flag --suite=sharding_clustered_collections is supplied, in which case it runs on clustered collections. The test supports the execution engine being either Classic or SBE. In one test case, SBE optimizes away a pipeline, but Classic does not. Prior to SERVER-74521 delivery, even when SBE was enabled, the CC case was still delegated to Classic, because SBE did not support CCs, so the behavior of the four conditions (Classic/SBE x non-CC/CC) was:
- Classic non-CC – pipeline present in the explain output
- Classic CC – pipeline present
- SBE non-CC – pipeline optimized away
- SBE CC that really still used Classic – pipeline present
Now that SBE supports CC, case 4 has changed to:
4. SBE CC – pipeline optimized away
The test needs to be updated to expect the SBE behavior now when it is run on the SBE x CC condition (#4).