Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
From: joshelser <git@git.apache.org>
To: dev@accumulo.apache.org
Reply-To: dev@accumulo.apache.org
References: <git-pr-104-accumulo@git.apache.org>
In-Reply-To: <git-pr-104-accumulo@git.apache.org>
Subject: [GitHub] accumulo pull request: ACCUMULO-4318 Made writers and scanners aut...
Content-Type: text/plain
Message-Id: <20160527213233.AE511DFC74@git1-us-west.apache.org>
Date: Fri, 27 May 2016 21:32:33 +0000 (UTC)
archived-at: Fri, 27 May 2016 21:32:35 -0000

Github user joshelser commented on the pull request:

    https://github.com/apache/accumulo/pull/104#issuecomment-222257863
  
    That's a very good point, @dhutchis. I think I've seen really weird things in the same manner where a BatchScanner falls out of scope, the finalizer closes it, and then invalidates the iterator being iterated over (in a for-each loop). I think @wjsl also hit this before.


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