You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2015/01/13 00:06:35 UTC

[jira] [Issue Comment Deleted] (PHOENIX-1428) Keep scanner open on server and pace by client instead of spooling

     [ https://issues.apache.org/jira/browse/PHOENIX-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Taylor updated PHOENIX-1428:
----------------------------------
    Comment: was deleted

(was: SUCCESS: Integrated in Phoenix-3.0-hadoop1 #313 (See [https://builds.apache.org/job/Phoenix-3.0-hadoop1/313/])
PHOENIX-1428 Queries with limit against tenant views is broken (jtaylor: rev 4e130d4d19f69ad42c936a6ccc4b5944dc916cb2)
* phoenix-core/src/main/java/org/apache/phoenix/execute/ScanPlan.java
* phoenix-core/src/it/java/org/apache/phoenix/end2end/TenantSpecificTablesDMLIT.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: Dave Hacker
>
> 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)