[
https://issues.jboss.org/browse/TEIID-1508?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-1508.
-----------------------------------
Resolution: Done
updated the dependent join logic to consider more accurately the affect of creating the
dependent join and moved consideration for dependent joins into the determination of join
ordering
Dependent join planning problem
-------------------------------
Key: TEIID-1508
URL:
https://issues.jboss.org/browse/TEIID-1508
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Affects Versions: 7.4
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 7.4
Without a dependent join hint a composite cross source dependent join will not plan
correctly unless the independent side can be pushed as a single query. The root of the
issue is that join planning involving more than 1 independent table does not consider the
effect of potential dependent joins early enough.
The workaround is to use a dependent join hint or set the cardinality of the independent
tables small enough to trigger the proper dependent join.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira