[
https://issues.jboss.org/browse/TEIID-2249?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2249:
---------------------------------------
What should be in scope for 8.4.1 is an initial form of 1.a, 1.b, with the ability provide
other possibly arbitrary hinting information.
I would propose that all other parts of the issue would be out of scope as to limit
support exposure with a possibly incomplete feature. However it will still be possible
through an extended translator to implement the desired functionality.
There should also be a configurable restiction threshold to prevent
the use of temp table if the tuple width is too wide
The current logic only passes key information to the source queries, so width isn't a
consideration unless there is an odd key type or some extreme composite key - which I
don't think he's referring to. The other possibility is that he means the
entirety of the independent/driving side of the join would be shipped to form the
temporary table such that the complete results are read by Teiid instead of a secondary
in-Teiid join being performed. That would be an entirely new mode of operation and would
be out of scope as well.
Enable the use of temporary tables for those data sources that
support them instead of IN criteria for EDS
----------------------------------------------------------------------------------------------------------
Key: TEIID-2249
URL:
https://issues.jboss.org/browse/TEIID-2249
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Reporter: Debbie Steigner
Assignee: Steven Hawkins
Fix For: 8.4.1
Our proposal is to allow for the more efficient use of large ad-hoc result-sets by rather
than creating a long 'IN' list, inserting them in to a temporary table - for
example a # table in Sybase and SQL Server - and then generating an SQL join to that
instead.
One of the difference to materialized views (or at least my understanding), is that this
work happens at a data-source rather than within the Teiid server.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira