[
https://issues.jboss.org/browse/TEIID-4498?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-4498:
---------------------------------------
The initial commit expanded the handling of the select clause to later in planning - for a
limited subset of queries, we can use a left outer join plan instead.
The next commit expanded handling further to new scalar subquery cases and the initial
handling of possible multi-row cases for scalar subqueries. Unfortunately we don't
yet handle composite keys.
The final commit will further generalize the multi-row case.
Generalize subquery batch processing
------------------------------------
Key: TEIID-4498
URL:
https://issues.jboss.org/browse/TEIID-4498
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Major
Fix For: 12.0
For subqueries that cannot be unnested, but can be modified to project their correlation,
we should have at least batch processing rather than the row by row default.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)