[
https://jira.jboss.org/jira/browse/TEIID-168?page=com.atlassian.jira.plug...
]
Steven Hawkins commented on TEIID-168:
--------------------------------------
re-added result set caching backed by the buffermanager. Since this is no longer a memory
cache, it's enabled by default with a size of 1024. It also means that xquery and
document model documents are cachable as well (since they are already backed by disk
stores). Result set caching can still be used through the cache execution property, but a
cache hint can also be used e.g.
/* cache */ select ....
The hint must be located at the start of the query and can only appear next to a select or
exec/execute.
No considerations are currently made for transactional state though.
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: 7.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 7.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