Hi everybody.
I've run across an unexpected behavior when using WholeRowIterator on a
BatchScanner. In case it matters, we're using cloudbase-1.3.4.
When I tell it to fetchColumnFamily(new Text(foo)) I get no results
back, though there are definitely records in that column family and in
On 07/09/2012 01:00 PM, John Vines wrote:
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
On Monday, July 9, 2012 1:14:09 PM, John Armstrong j...@ccri.com wrote:
On 07/09/2012 01:00 PM, John Vines wrote:
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
John,
This was a fun one, but we figured it out. Thanks for providing code --
that helped a lot. The quick workaround is to set the priority of the
WholeRowIterator to 21, above the VersioningIterator. Turns out the two
iterators are not commutative, so order matters.
Solution: when you set up
