[
https://issues.jboss.org/browse/TEIID-2481?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-2481.
-----------------------------------
Fix Version/s: 8.8
(was: 8.10)
Resolution: Done
Marking as resolved against 8.8, since that is where we allowed mergable view layers. Of
the other improvements, the only one that seems like it should be tackled proactively is
the inlining when common table expressions are not supported. This is not however a good
fit with planning currently as we would most naturally make that decision prior to
optimization, which means more than likely there would be multiple references. So I'm
resolving for now and we can revisit as needed.
common table (with) push down improvements
------------------------------------------
Key: TEIID-2481
URL:
https://issues.jboss.org/browse/TEIID-2481
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.8
The general strategy for with pushdown should better handle:
- a with clause that can be pushed against a source that does not support common table.
If a single reference or some other sufficient condition is met then we should just inline
the pushdown rather than inhibiting the whole query from pushing down.
- even if a source supports with pushdown, it may be more performant in some
circumstances to inline the common table reference (such as only a single reference).
This is complicated slightly by subqueries.
- alternatively in some situations even if a with clause can be pushed, it may be better
to not perform the pushdown -e.g. two separate pushdown accesses to a common table that is
expensive to compute (this may need to be hint driven).
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)