[teiid-issues] [JBoss JIRA] Commented: (TEIID-1473) Don't batch more rows than is needed when query contains limit but translator does not support limit

[Steven Hawkins (JIRA)]

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

Steven Hawkins commented on TEIID-1473:
---------------------------------------

Yes, I can change the batch size as well.  I'll still have to adjust the engine logic though to not pull additional rows.

> Don't batch more rows than is needed when query contains limit but translator does not support limit
> ----------------------------------------------------------------------------------------------------
>
>                 Key: TEIID-1473
>                 URL: https://issues.jboss.org/browse/TEIID-1473
>             Project: Teiid
>          Issue Type: Enhancement
>            Reporter: Howard Abrams
>            Assignee: Steven Hawkins
>            Priority: Minor
>
> Teiid shouldn't try to batch more rows than is needed when query contains limit and translator does not support limit.
> For example, say there is a translator that exposes a table "A", but does not support limit.
> select * from A limit 2
> will currently select an entire batch of rows (1024?) from A, instead of just stopping after 2 rows.
> Likewise, if the translator supports neither offset nor limit, and the query contains both, Teiid should not try to batch more that (offset + limit) rows.
> This is marked as "Minor" because the workaround of naively supporting limit and offset within a translator is not too hard.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira