[
https://jira.jboss.org/jira/browse/TEIID-196?page=com.atlassian.jira.plug...
]
Steven Hawkins updated TEIID-196:
---------------------------------
Component/s: Connector API
Query Engine
Fix Version/s: 6.1.0
Affects Version/s: 6.0.0
Affects: [Documentation (Ref Guide, User Guide, etc.),
Compatibility/Configuration, Release Notes]
Complexity: High
Support creation of temp tables on physical sources.
----------------------------------------------------
Key: TEIID-196
URL:
https://jira.jboss.org/jira/browse/TEIID-196
Project: Teiid
Issue Type: Feature Request
Components: Connector API, Query Engine
Affects Versions: 6.0.0
Reporter: Ken Johnson
Fix For: 6.1.0
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 contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira