BigTable did not define LSM iterators. In the context of LSM iterators, I think of the system as an online sort of the data that continually pulls sorted subsets of the data through the iterator stack. Sorting data does not imply making it unique. Giving iterators access to all data gives them the greatest level of flexibility.
On Thu, Dec 22, 2011 at 5:24 PM, Aaron Cordova <[email protected]> wrote: > If you want to make it possible for the user to turn this functionality off - > (let's call it the "GO MULTIMAP!!" option) that's fine with me, as long as by > default it's turned on. > > > On Dec 22, 2011, at 5:23 PM, Keith Turner wrote: > >> On Thu, Dec 22, 2011 at 5:15 PM, Aaron Cordova <[email protected]> wrote: >>> I propose Accumulo drops all but one arbitrarily >>> >> Ok, the default configuration currently does this. Like I said in >> another comment Eric suggested sorting on the value in this case so >> that its not arbitrary, and scans behave deterministically. >> >> In the case where the user starts modifying the iterator stack, I >> suppose you want an iterator that users can not see or override/remove >> that does this? That is not something I would advocate for? >> >> Keith >
