-
Type:
New Feature
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Query
-
None
-
8
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Add JOIN support to the MQL translator. Supported join shapes:
- INNER JOIN with a single-field equijoin ON condition
- LEFT OUTER JOIN with a single-field equijoin ON condition
- JOIN FETCH (transparent — produces the same SQL AST as a plain JOIN)
- Chained joins (A→B→C)
Implementation: Each join translates to a $lookup + $unwind stage pair prepended to the aggregation pipeline. Joined-table columns are referenced as dotted paths (e.g., o1_0.total) in all downstream stages.
Out of scope (throws FeatureNotSupportedException with a Jira ticket reference): RIGHT OUTER JOIN, FULL OUTER JOIN, CROSS JOIN, compound equijoin ON conditions (composite PKs), non-equijoin ON conditions, non-column ON expressions, LATERAL UNNEST joins, and subquery joins. Follow-up tickets are filed for each.
- is depended on by
-
HIBERNATE-161 Support RIGHT OUTER JOIN queries
-
- Backlog
-
-
HIBERNATE-162 Support FULL OUTER JOIN queries
-
- Backlog
-
-
HIBERNATE-163 Support CROSS JOIN queries
-
- Backlog
-
-
HIBERNATE-164 Support compound equijoin ON conditions (composite primary keys)
-
- Backlog
-
-
HIBERNATE-165 Support non-equijoin ON conditions
-
- Backlog
-
-
HIBERNATE-166 Support non-column expressions in join ON conditions
-
- Backlog
-
-
HIBERNATE-167 Support subquery joins (derived-table joins)
-
- Backlog
-
- is related to
-
HIBERNATE-65 Feature: Entity Association Support
-
- Needs Triage
-