On Wed, Feb 15, 2012 at 1:14 PM, Keith Turner <[EMAIL PROTECTED]> wrote:
> Yeah I think you have listed the options correctly. To be exhaustive,
> I suppose another option is to do the row selection/filtering on the
> client side and not use an iterator.
> If you happen to chose to write a custom iterator, you might as well
> write the iterator described in ACCUMULO-403, extend it, and post a
> patch :)
Once I'm working on 1.4, where I have some chance of actually using a
patch that I post, I'll be much more patch-prone.
> On Wed, Feb 15, 2012 at 12:40 PM, Benson Margulies
> <[EMAIL PROTECTED]> wrote:
>> So, in 1.3.5 ...
>> If the idea I need to express is:
>> Given a constraint on range, cf, cq:
>> for each row that matches the constraint
>> return the cell that matched the constraint plus some other
>> cells specified by cf/cq
>> For now, I could use the attributes of a scanner to express the
>> constraint, and then WholeRowIterator (if I can afford the memory)
>> or I can write my own iterator
>> or I can wait for the thing described in the jira?