[
https://jira.jboss.org/jira/browse/TEIID-168?page=com.atlassian.jira.plug...
]
Ramesh Reddy commented on TEIID-168:
------------------------------------
As the description noted this will based upon the buffer manager, not on JBoss Cache. It
will be be per VM, not distributed. The idea here is not to cache the end user result
sets, but cache the intermediate results that are based on the source results based on
design time hints. Thus effectively reproducing the user result set faster even in the
case user has a modified query. Much like dynamic staging tables.
Remove resultset caching
------------------------
Key: TEIID-168
URL:
https://jira.jboss.org/jira/browse/TEIID-168
Project: Teiid
Issue Type: Feature Request
Components: JDBC Connector, Query Engine
Affects Versions: 6.x
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 6.1.0
Resultset caching should be replaced with relation and procedure caching. This would
initially be backed by the buffermanager, based upon hints/costing, and be utilized by the
planner rather than the resolver. It would be good if we also detected the level of
determinism.
--
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