Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
From: ivakegg <git@git.apache.org>
To: dev@accumulo.apache.org
Reply-To: dev@accumulo.apache.org
References: <git-pr-260-accumulo@git.apache.org>
In-Reply-To: <git-pr-260-accumulo@git.apache.org>
Subject: [GitHub] accumulo issue #260: ACCUMULO-4643 initial implementation
Content-Type: text/plain
Message-Id: <20170530140133.0B058DFC8B@git1-us-west.apache.org>
Date: Tue, 30 May 2017 14:01:33 +0000 (UTC)
archived-at: Tue, 30 May 2017 14:01:35 -0000

Github user ivakegg commented on the issue:

    https://github.com/apache/accumulo/pull/260
  
    I am pretty satisfied this is now working as designed.  The test case uses an iterator that will throw a yield exception every other next and every other seek.  The test case also detects when the iterator has been torn down and rebuilt.  From the client perspective, nothing changes (all keys returned appropriately).


---
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.
---