-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Optimization
-
Fully Compatible
-
None
-
None
-
None
-
None
-
None
-
None
-
None
An earlier ticket (SERVER-112725) checked for non-existent collections in executor.cpp and the same check also inadvertently passed for sharded collections. As a result, the tests in lookup_sharded_no_join_opt.js passed for sharded collections even without my new code because this check is triggered in executor.cpp
if (mca.isAnySecondaryNamespaceAViewOrNotFullyLocal())
The correct check is to check if sharding is enabled on any of the foreign collections. The test now passes with my code as my new check is correctly triggered.
- is related to
-
SERVER-112725 Ensure internalEnableJoinOptimization works with sharded clusters
-
- Closed
-
-
SERVER-112239 Support views for join reordering
-
- Needs Scheduling
-