Thanks for the update, that is very useful!
On Tue, Jul 12, 2011 at 3:16 PM, Philippe wrote:
> Hi Jonathan,
> Thanks for the answer, I wanted to report on the improvements I got because
> someone else is bound to run into the same questions...
>
>>
>> > C) I want to access a key that is at the 50
Hi Jonathan,
Thanks for the answer, I wanted to report on the improvements I got because
someone else is bound to run into the same questions...
> > C) I want to access a key that is at the 50th position in that table,
> > Cassandra will seek position 0 and then do a sequential read of the file
>
Ah, I get it. Your normal access pattern should be one row at a time.
On Sun, Jul 3, 2011 at 11:41 AM, David Boxenhorn wrote:
>>> What do you think ?
>>
>> I think you should strongly consider denormalizing so that you can
>> read ranges from a single row instead.
>
> Why do you recommend denorma
>> What do you think ?
>
> I think you should strongly consider denormalizing so that you can
> read ranges from a single row instead.
Why do you recommend denormalizing instead of secondary indexes?
On Fri, Jun 24, 2011 at 3:58 PM, Philippe wrote:
> A) Upon opening an SSTTable for read, Cassandra samples one key in 100 to
> speed up disk access.
Close enough.
> Is the percentage configurable ?
# The Index Interval determines how large the sampling of row keys
# is for a given SSTable. The
Hello,
I am trying to understand the way cassandra reads data. I've been reading a
lot and here is what I understand.
Can I get some feedback on the following claims ? Which are right and which
are wrong?
A) Upon opening an SSTTable for read, Cassandra samples one key in 100 to
speed up disk acce
