Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.3.0-rc0
Affects Version/s: None
Component/s: None
Labels:
- M2

Assigned Teams:

Query Optimization
Backwards Compatibility:
Fully Compatible
CAR Domain/s:
None

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

Currently the random join reorderer will always produce plans with CollectionScans and NestedLoopJoins. As a next step, we should produce plans with Indexed nested loop joins when a satisfying index on the inner collection exists.

is duplicated by

SERVER-111584 Investigate building QSNs involving INLJ in the join optimizer

Closed

related to

SERVER-111222 Stage builder translation from IndexedNestedLoopJoinEmbeddingNode to SBE

In Code Review

SERVER-112939 Use better heuristic for picking the best index for INLJ plans

Closed

Assignee:: Ben Shteinfeld
Reporter:: Ben Shteinfeld
Participants:: Ben Shteinfeld, Githook User
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Oct 10 2025 07:28:48 PM UTC
Updated:: Nov 12 2025 04:13:17 AM UTC
Resolved:: Nov 04 2025 05:56:41 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates