Loading...

XML

Word

Printable

JSON

Type: New Feature
Resolution: Duplicate
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Query Optimization
CAR Domain/s:
None

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

Make sure we're not running join optimization on every getNext() call in a DSLookup

duplicates

SERVER-120796 Confirm nested lookup subpipelines are not eligible for join re-ordering on their own

Closed

Assignee:: Unassigned
Reporter:: Alya Berciu
Participants:: Alya Berciu
Votes:: 0 Vote for this issue
Watchers:: 1 Start watching this issue

Created:: Jan 26 2026 08:20:02 PM UTC
Updated:: Mar 12 2026 03:36:20 PM UTC
Resolved:: Mar 12 2026 03:36:20 PM UTC