[
https://issues.apache.org/jira/browse/PHOENIX-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15090333#comment-15090333
]
Hudson commented on PHOENIX-1428:
---------------------------------
SUCCESS: Integrated in Phoenix-master #1060 (See
[https://builds.apache.org/job/Phoenix-master/1060/])
PHOENIX-1428 Keep scanner open on server and pace by client instead of
(samarth: rev 150a50e40c785c3b10ebd74466582cfb07f98daf)
* phoenix-core/src/it/java/org/apache/phoenix/monitoring/PhoenixMetricsIT.java
* phoenix-core/src/main/java/org/apache/phoenix/execute/ScanPlan.java
* phoenix-core/src/main/java/org/apache/phoenix/execute/AggregatePlan.java
* phoenix-core/src/test/java/org/apache/phoenix/query/QueryServicesTestImpl.java
* phoenix-core/src/main/java/org/apache/phoenix/util/ScanUtil.java
*
phoenix-core/src/it/java/org/apache/phoenix/end2end/SpooledTmpFileDeleteIT.java
> 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
> Assignee: Samarth Jain
> Labels: SFDC
> Fix For: 4.7.0
>
> Attachments: PHOENIX-1428.patch, PHOENIX-1428_v2.patch
>
>
> 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)
