Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
From: ohshazbot <git@git.apache.org>
To: dev@accumulo.apache.org
Reply-To: dev@accumulo.apache.org
References: <git-pr-33-accumulo@git.apache.org>
In-Reply-To: <git-pr-33-accumulo@git.apache.org>
Subject: [GitHub] accumulo pull request: ACCUMULO-3646 Update iterator doc on
 entrie...
Content-Type: text/plain
Message-Id: <20150427173527.3CB04E179A@git1-us-west.apache.org>
Date: Mon, 27 Apr 2015 17:35:27 +0000 (UTC)

Github user ohshazbot commented on a diff in the pull request:

    https://github.com/apache/accumulo/pull/33#discussion_r29169794
  
    --- Diff: docs/src/main/asciidoc/chapters/iterator_design.txt ---
    @@ -145,8 +146,16 @@ alter the internal state of the Iterator.
     
     These methods simply return the current Key-Value pair for this iterator. If `hasTop` returns true,
     both of these methods should return non-null objects. If `hasTop` returns false, it is undefined
    -what these methods should return. Multiple calls to these methods should not alter the state
    -of the Iterator like `hasTop`.
    +what these methods should return. Like `hasTop`, multiple calls to these methods should not alter 
    +the state of the Iterator.
    +
    +When saving a Key or Value from a source iterator's `getTopKey` or `getTopValue` methods
    +for use after calling `next` on the source iterator (e.g., when cacheing keys or values
    +from the source iterator), it is important to copy the Key or Value into a new object 
    +because the source iterator may reuse the Key or Value objects for performance reasons.
    --- End diff --
    
    I don't like the verb use, as it's vague. I would prefer specifics - ..."which does not modify or cache the key beyond calling next()"...


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---