[
https://issues.jboss.org/browse/TEIID-1473?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1473:
---------------------------------------
It would be best for each translator to implement limit handling, since the translator may
already be setting batch sizes or other settings based upon the assumption of returning a
full batch. There is also already compensation logic in the engine if a translator does
support limit, but does not support offset.
I'll also look at adding catch all logic in the engine if limit is not supported.
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