[
https://issues.jboss.org/browse/TEIID-587?page=com.atlassian.jira.plugin....
]
Steven Hawkins resolved TEIID-587.
----------------------------------
Resolution: Out of Date
Marking as out of date. The specific salesforce issues listed above have been worked
around. The remaining central salesforce issue is that we limit pushdown to a single join
- but that is more of a translator limitation than an engine issue at this point. There
is also TEIID-3531 that serves as a general join planning issue.
Better pushdown support for exotic joins
----------------------------------------
Key: TEIID-587
URL:
https://issues.jboss.org/browse/TEIID-587
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 6.1.0
Reporter: Steven Hawkins
Fix For: 11.x
Our optimizations get in the way of Salesforce pushdown. Specifically rewriting like when
possible to = and converting outer joins to inner joins. In both cases we would need to
not perform the optimization in the first place or convert into an acceptable form prior
to pushdown.
The next is that salesforce, while requiring key criteria also allows other criteria in
the left outer join on clause (which would be the same as having criteria on the nested
relationship query in the salesforce query). With the capabilities as currently defined
this would cause the query to not be pushed down. We should consider adding a relational
supported join criteria type that requires key criteria but allows for outside criteria.
Also we should treat the lack of inner join support to mean that criteria on the inner
side of an outer join cannot be pushed.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)