[
https://issues.apache.org/jira/browse/PHOENIX-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14205197#comment-14205197
]
Jeffrey Zhong commented on PHOENIX-1395:
----------------------------------------
[~lhofhansl] That will be ideal. In some cases, we can't avoid the data spill
but it seems now we're way easier to spill data to disk than it should be. Even
in case that we scan the full table, we can return chunked results per each
resultset.next() invocation.
> ResultSpooler spill files are left behind in /tmp folder
> --------------------------------------------------------
>
> Key: PHOENIX-1395
> URL: https://issues.apache.org/jira/browse/PHOENIX-1395
> Project: Phoenix
> Issue Type: Bug
> Reporter: Jeffrey Zhong
> Assignee: Alicia Ying Shu
> Fix For: 4.2
>
> Attachments: PHOENIX-1395.patch
>
>
> Recently we found that some ResultSpooler*.bin files left in the tmp folder.
> I think those are due to some client code doesn't call close on the returned
> Resultset(which internally will invoke underlying
> OnDiskResultIterator.close()) or client code get killed during result
> iterating.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
