[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:comment-tabpanel&focusedCommentId=12705747#comment-12705747 ] 

Steven Hawkins commented on TEIID-2098:
---------------------------------------

Modified the preparedplan logic to add a limit to the command.  Also added the ability to get the final buffer from more nodes and tunneled the affect of setting the max rows.

Still need to handle cached result sets.
                
> 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