We have an open bug report about how Mock handles the reuse of Values. I'm wondering if perhaps there is a conflict there with BatchScanner in the same vain. More likely though, it's probably a case of BatchScanner behaving like a Scanner in Mock due to the non-distributed nature of Mock. I'm not really sure how we could expand the MockAccumulo framework to be MockParallel though.
John On Mon, Jul 9, 2012 at 12:55 PM, John Armstrong <[email protected]> wrote: > On 07/09/2012 12:42 PM, John Armstrong wrote: > >> I've run across an unexpected behavior when using WholeRowIterator on a >> BatchScanner. >> > > addendum: This does not seem to happen when using the MockCloudbase > framework, so it didn't show up in my unit tests. If this is intentional > behavior, MockCloudbase should probably behave the same way as the real > thing, no? >
