Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 9.0.0-rc0
Affects Version/s: None
Component/s: None
Labels:
- joo-fallback

Assigned Teams:

Query Optimization
Backwards Compatibility:
Fully Compatible
Linked BF Score:
200
CAR Domain/s:
None

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

List of collections we should ban:

Timeseries collections
Clustered collections
Sharded collections
Capped collections
Oplog
Collections with a collation

is duplicated by

SERVER-114737 Join Optimization: wrong result with optimized plan + timeseries

Closed

related to

SERVER-114737 Join Optimization: wrong result with optimized plan + timeseries

Closed

SERVER-114739 Join Optimization: collation disregarded when joining

Closed

SERVER-114763 Do not use join optimizer if any involved collections are sharded (not just the base)

Closed

SERVER-125401 Only shorten the joo-eligible prefix of a query rather than completely falling back for ineligible collections

Open

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

Created:: Apr 23 2026 02:51:19 PM UTC
Updated:: May 07 2026 08:19:24 AM UTC
Resolved:: Apr 30 2026 03:36:03 PM UTC