[
https://jira.jboss.org/jira/browse/TEIID-168?page=com.atlassian.jira.plug...
]
Steven Hawkins commented on TEIID-168:
--------------------------------------
That's a mischaracterization of what is happening. It's just an intermediate
state that the memory backed used for connector result sets was moved to jboss cache.
JBoss cache without additional work is not appropriate for large data volumes requiring
intelligent paging, which is the desired end state of this feature.
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