Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
MIME-Version: 1.0
References: <1447786817388-15586.post@n5.nabble.com>
 <1447795370371-15587.post@n5.nabble.com>
 <564BA1B1.3060904@gmail.com> <1447946111053-15598.post@n5.nabble.com>
 <CAL5zq9Z0wRciQHqqMiJ_pfgoqN+EGO9SP-oBUVV5YTdGZLNVKg@mail.gmail.com>
 <1447954980608-15600.post@n5.nabble.com>
In-Reply-To: <1447954980608-15600.post@n5.nabble.com>
From: Christopher <ctubbsii@apache.org>
Date: Thu, 19 Nov 2015 18:56:48 +0000
Message-ID: 
 <CAL5zq9Z-iUmwucKWgD4whH64nC9yZatvcv8fWN0UnEyNUnkH6w@mail.gmail.com>
Subject: Re: hasNext throws weird exception
To: dev@accumulo.apache.org
Content-Type: multipart/alternative; boundary=94eb2c064ab4c034880524e952b1

--94eb2c064ab4c034880524e952b1
Content-Type: text/plain; charset=UTF-8

When you call the iterator method on a scanner, Accumulo instantiates a
bunch of internal data structures that are specific to that iterator/query.
Scanner is basically a configuration object which has iterator as a factory
method. The iterator is really what does the query work. Calling iterator
multiple times creates multiple, independent queries.

On Thu, Nov 19, 2015, 12:44 z11373 <z11373@outlook.com> wrote:

> Thanks Christopher! What are those separate iterations? The scanner object
> was not shared (besides it's only single thread), and also my test app is
> the only client app running at that time.
> I am just curious, however, the code you suggested is a good practice, and
> I'll keep in mind.
>
> Thanks,
> Z
>
>
>
> --
> View this message in context:
> http://apache-accumulo.1065345.n5.nabble.com/hasNext-throws-weird-exception-tp15586p15600.html
> Sent from the Developers mailing list archive at Nabble.com.
>

--94eb2c064ab4c034880524e952b1--