[
https://issues.jboss.org/browse/TEIID-5683?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5683:
---------------------------------------
There are nuances to the pushing logic that make it hard to simply change into a simple
detection for earlier costing. Running the rule early violates some existing assumptions,
such at the final output element assignment has already been run. So there isn't a
very quick fix here. I'll see if some new code will help.
Push or use limit information before dependent join processing
--------------------------------------------------------------
Key: TEIID-5683
URL:
https://issues.jboss.org/browse/TEIID-5683
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Major
Fix For: 12.2
There appear to be some situations (such as a left outer join from TEIID-5680) where the
limit could help direct a dependent join, but isn't considered as rule push limit
isn't run until later.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)