[teiid-issues] [JBoss JIRA] Commented: (TEIID-168) Remove resultset caching

[Steven Hawkins (JIRA)]

    [ https://jira.jboss.org/jira/browse/TEIID-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12453353#action_12453353 ] 

Steven Hawkins commented on TEIID-168:
--------------------------------------

Per VM is an initial design restriction based upon re-using the buffer manager logic.  It is another line of work to re-implement the caching mechanisms of the buffer manager through jboss cache.  

I think you are overstating the case of limiting the usefulness.  Caching relations (with scope determined by level of determinism) should have roughly the same performance curve with or without distribution.  You would tend to just populate the caches faster with distribution.

Along similar lines of thought, the case could be made for moving end user result set caching to the client vm.  This defect should really only cover connector result set caching.

> 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