[
https://issues.jboss.org/browse/TEIID-2249?page=com.atlassian.jira.plugin...
]
Debbie Steigner edited comment on TEIID-2249 at 6/17/13 9:00 AM:
-----------------------------------------------------------------
Customer RBS input:
Hi Erica
I had a read of the temp table documentation for Teiid 8.3 and I am unsure whether it
meets our full requirement. It is a good start having the ability to create source temp
table.
As it stands, the temp table has to be predefined before the execution of the query and
seems like have to be done in a teiid stored procedure.
Our requirement, is the creation of source temp table will be done in the background by
Teiid during runtime of a query and dependent join is pushed down to source to do the join
locally at the source.
It is basically shipping the temp data into target source for joining to improve the
performance.
It will be good if we can also hint the query to specify when to use this temp table join
or set a threshold value if there are more than X no. Of values in IN clause switch to use
this method.
And potentially creating an index on the source temp table on the joining columns and also
the ability to specify source system hints too.
Thanks
Nelson
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