[
https://issues.apache.org/jira/browse/PHOENIX-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14206088#comment-14206088
]
Lars Hofhansl commented on PHOENIX-1428:
----------------------------------------
I think the full scan with LIMIT and no WHERE is a special case we should
optimize anyway (i.e. execute this always with a single scan).
For other cases, yes, we should not spool on the client, but just pace the
scanners on the servers. (for some things like joins, etc, where the data does
not exist as such on the server that might be hard/not-possible).
> 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)
