[
https://issues.apache.org/jira/browse/PHOENIX-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055412#comment-14055412
]
Hudson commented on PHOENIX-539:
--------------------------------
SUCCESS: Integrated in Phoenix | 3.0 | Hadoop1 #126 (See
[https://builds.apache.org/job/Phoenix-3.0-hadoop1/126/])
PHOENIX-539 Chunked loading of parallel scanning (gabrielr: rev
ec1b76ab28880d548c8061a6dcb80a6fe0d97ed6)
*
phoenix-core/src/main/java/org/apache/phoenix/iterate/ChunkedResultIterator.java
* phoenix-core/src/main/java/org/apache/phoenix/query/QueryServicesOptions.java
* phoenix-core/src/main/java/org/apache/phoenix/compile/StatementContext.java
* phoenix-core/src/it/java/org/apache/phoenix/end2end/QueryIT.java
* phoenix-core/src/main/java/org/apache/phoenix/query/QueryServices.java
* phoenix-core/src/main/java/org/apache/phoenix/iterate/ParallelIterators.java
* phoenix-core/src/main/java/org/apache/phoenix/join/HashJoinInfo.java
* phoenix-core/src/main/java/org/apache/phoenix/execute/ScanPlan.java
> Implement parallel scanner that does not spool to disk
> ------------------------------------------------------
>
> Key: PHOENIX-539
> URL: https://issues.apache.org/jira/browse/PHOENIX-539
> Project: Phoenix
> Issue Type: Task
> Reporter: James Taylor
> Assignee: Gabriel Reid
> Fix For: 5.0.0, 3.1, 4.1
>
> Attachments: PHOENIX-539.1.patch, PHOENIX-539.patch
>
>
> In scenarios where a LIMIT is not present on a non aggregate query that will
> return a lot of results, Phoenix spools the results to disk. This is less
> than ideal in these situations. @larsh has created a very good and relatively
> simple implementation that is queue based to replace this.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
