Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
- explain

Assigned Teams:

Query Execution
Case:
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

When issuing explain() on aggregate commands with $lookup in it, 'indexesUsed' field is populated with the index that was used as part of the $lookup stage. However, this doesn't happen when $lookup is run on the sharded collection.

This makes it hard to debug and understand which index was used, for both users and us.

is related to

SERVER-88561 Expand explain command output for $graphLookup stage

Backlog

SERVER-22622 Improve $lookup explain to indicate query plan on the "from" collection

Needs Scheduling

related to

SERVER-105668 Avoid reporting 'indexesUsed' for $lookup in sharded collections

Backlog

SERVER-1812 Add the ability to get query results and the query plan in one call

Backlog

Assignee:: Unassigned
Reporter:: Denis Grebennicov
Participants:: Denis Grebennicov
Votes:: 0 Vote for this issue
Watchers:: 8 Start watching this issue

Created:: Apr 02 2024 04:08:27 PM UTC
Updated:: Sep 23 2025 08:37:56 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates