: OrderPreservingPartitioner for get_range_slices
My experience for the last question is ... it depends. If you have NO
changes to the store (which I would argue could be abnormal, it's not in a
production environment allowing writes) ... then I you can do a full
range/key scan and get no repeats. Fa
My experience for the last question is ... it depends. If you have NO
changes to the store (which I would argue could be abnormal, it's not in a
production environment allowing writes) ... then I you can do a full
range/key scan and get no repeats. Factors that will impact scanning all
keys includ
And what about uniqueness? Can we be sure that we get each row just once?
Thanks.
2010/9/15 Janne Jalkanen
>
> Correct. You can use get_range_slices with RandomPartitioner too, BUT the
> iteration order is non-predictable, that is, you will not know in which
> order you get the rows (RandomPart
Correct. You can use get_range_slices with RandomPartitioner too, BUT
the iteration order is non-predictable, that is, you will not know in
which order you get the rows (RandomPartitioner would probably better
be called ObscurePartitioner - it ain't random, but it's as good as if
it were
