It doesn't have to be an iterator that can't be turned off, just one that's enabled by default.
On Dec 22, 2011, at 5:32 PM, Keith Turner wrote: > On Thu, Dec 22, 2011 at 5:23 PM, Aaron Cordova <[email protected]> wrote: >> And just to be clear, since there are several definitions of key flying >> around - in the following case: >> >> row1,colfam1,colqual1,4 -> valueA >> row1,colfam1,colqual1,5 -> valueB >> >> These can coexist peacefully - although the versioning iterator might >> supress all but k versions. >> >> in this case: >> >> row1,colfam1,colqual1,4 -> valueA >> row1,colfam1,colqual1,4 -> valueB >> >> Accumulo should throw one away arbitrarily. I think what you mentioned, a >> system iterator that performs this logic, would be a good implementation. > > I am opposed to making this a system iterator. I like iterators > seeing the data in sorted form, not "sort -u" :)
