[
https://issues.jboss.org/browse/TEIID-196?page=com.atlassian.jira.plugin....
]
Steven Hawkins commented on TEIID-196:
--------------------------------------
The simplest (lowest effort) design would be an extension of our DDL/temp table syntax:
CREATE FOREIGN TEMPORARY TABLE name (...) ON source [AS 'native sql']
The options clauses would specify the name in source etc as appropriate and the native sql
would be executed via the native query procedure facility if applicable. This side-steps
any need in our language to add support for additional source constructs, such as
alternative index types, additional constraints etc. So this would effectively be a
hybrid of our internal temp logic and standard pushdown logic.
We would also likely have to allow a drop to be specified with native sql. We might want
to still perform some metadata import from the source as to not make the full metadata
specification too onerous. From the perspective of Teiid this will be treated as a
temporary table in so much as it will be session scoped, but there would not need to be a
restriction on the source side as to the table type.
Support creation of temp tables on physical sources.
----------------------------------------------------
Key: TEIID-196
URL:
https://issues.jboss.org/browse/TEIID-196
Project: Teiid
Issue Type: Feature Request
Components: Connector API, Query Engine
Affects Versions: 6.0.0
Reporter: Ken Johnson
Fix For: 8.3
This is a multi-part request.
First, the system should support creation of temporary tables using a physical backing
store rather than buffer manger. Given multi-pass SQL's heavy use of temp tables,
buffer manager can easily be overloaded with large interim results stored in temp tables.
Second, this should be a user-configurable behavior. For example, user might be able to
choose a system-level or session-level default from among:
-- memory/cache
-- a source represented by a connector binding
-- a distinct temp source defined with it's own connection parameters (possibly
another schema in the repository DB instance)
Ideally default selectoin should be override-able at temp table creation time through a
DDL extension
In the case where multiple temp tables have been created on a source via connector, the
query planner should recognize this and leverage pushdown to the temp store when later
query passes access multiple temp tables.
--
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