[teiid-issues] [JBoss JIRA] (TEIID-2098) Caching does not interact well with Statement.setMaxRows

[Steven Hawkins (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins resolved TEIID-2098.
-----------------------------------

    Resolution: Done


Added a rowLimit field to the cache results so that if more results are requested and an incomplete result is found, it will not be used.  This could also be used to populate partial cache entries when the entire result is not read, but that was not added.
                
> Caching does not interact well with Statement.setMaxRows
> --------------------------------------------------------
>
>                 Key: TEIID-2098
>                 URL: https://issues.jboss.org/browse/TEIID-2098
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: Query Engine
>    Affects Versions: 7.0
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>             Fix For: 8.1
>
>
> Most of the time setting maxRows will cause the plan to not be cachable and the results will be cached/reused regardless of what subsequent maxRows are set to.
> Finally a general issue is that if the query cannot have maxRows set as a limit (if there is already a limit or it's a procedure call) then the maxRows is ignored.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira