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 <[email protected]> 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. >
