[
https://issues.jboss.org/browse/TEIID-4498?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-4498:
---------------------------------------
I can't make this work easily with the existing logic - it presumes that the subquery
will drive a dependent join. With a project subquery we need the reverse. Dependent
access nodes currently don't cross subplans. So either I need to rewrite the logic to
line the plan or take another approach.
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)