On Sat, Jul 21, 2012 at 3:37 PM, Sylvain Lebresne wrote:
>> I don't know much about Cassandra internals, but from a user point of
>> view, a scan for a range of tokens is not a common use-case.
>
> All of boostrap/move/decommission/repair rely heavily on being able to
> scan efficiently a range of
On Sat, Jul 21, 2012 at 12:04 AM, Kirk True wrote:
> I was aware of the read-then-write pattern for counters, but not secondary
> indexes. I'll have to take a look into that.
Fyi, if you are interested by the subject,
https://issues.apache.org/jira/browse/CASSANDRA-2897 is relevant.
--
Sylvain
> I don't know much about Cassandra internals, but from a user point of
> view, a scan for a range of tokens is not a common use-case.
All of boostrap/move/decommission/repair rely heavily on being able to
scan efficiently a range of token. Otherwise, a
boostrap/move/decommission/repair of a node