[
https://issues.apache.org/jira/browse/PHOENIX-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14205210#comment-14205210
]
Jeffrey Zhong commented on PHOENIX-1428:
----------------------------------------
This is a very good improvement even without limit clause when there is no
order by clauses in the query. ChunkedResultIteratorFactory should not use
SpoolingResultIterator at all. Thanks.
> Keep scanner open on server and pace by client instead of spooling
> ------------------------------------------------------------------
>
> Key: PHOENIX-1428
> URL: https://issues.apache.org/jira/browse/PHOENIX-1428
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
>
> Instead of spooling a batch of results for all chunked scans to the client,
> keep the scan open and pace it through pre-fetching. This will perform much
> better for a full table scan with a LIMIT = 1, as this case currently will
> run a scan for every guidepost, each returning a single row.
> [~lhofhansl]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
