You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2014/01/09 22:05:51 UTC

[jira] [Commented] (ACCUMULO-1280) Add close method to iterators

    [ https://issues.apache.org/jira/browse/ACCUMULO-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867051#comment-13867051 ] 

Christopher Tubbs commented on ACCUMULO-1280:
---------------------------------------------

Might be nice if, in the close method, we knew why it was closed... such as because the scan completed (eg. an iterator on top of it finished) or because the scan was preempted, or if a task was interrupted (canceled compaction, or scan session timeout). Some of these cases might warrant additional methods instead of adding params to the close method, or the information could be available in the iterator environment somehow.

> Add close method to iterators
> -----------------------------
>
>                 Key: ACCUMULO-1280
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1280
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: Keith Turner
>
> It would be useful if Accumulo iterators had a close method.  Accumulo would call this when its finished using the iterator stack.
> How would this work w/ isolation?
> Is it ok to break the iterator API?



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)