-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Minor - P4
-
None
-
Affects Version/s: 8.0.9, 8.3.0-rc0
-
Component/s: None
-
None
-
Query Optimization
-
ALL
-
None
-
None
-
None
-
None
-
None
-
None
-
None
When using $lookup where the foreign collection is a view that contains $unionWith, the explain output's $lookup stage does not include the all indexes in the indexesUsed field that were used in the execution of the view. This differs from executing the same pipeline without the view, where indexesUsed is properly populated, making it difficult to analyze query performance when views are involved.
See attached indexesUsedrepro.js
for steps to reproduce this problem.
- is related to
-
SERVER-105668 Avoid reporting 'indexesUsed' for $lookup in sharded collections
-
- Backlog
-
-
SERVER-88883 Report 'indexesUsed' for $lookup over sharded collections
-
- Needs Scheduling
-