[
https://issues.apache.org/jira/browse/PHOENIX-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14062662#comment-14062662
]
Maryann Xue commented on PHOENIX-539:
-------------------------------------
Thanks, [~jamestaylor]! I tried setting batch size to 2 for HashJoinTest. And
it turned out that the cache close was not a problem, but the
ChunkedResultIterator still could not work with hash join scan for the reason
that:
a single row in the left table can produce multiple rows after joining
the right table (hash cache) and if a batch stops in the middle of such
multiple results then when the next batch starts the leftover of those multiple
results (produced by the previous row) will be lost.
> 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)
