incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aaron morton <aa...@thelastpickle.com>
Subject Re: why set replica placement strategy at keyspace level ?
Date Fri, 01 Feb 2013 17:44:24 GMT
Many of my mental models bother people :)

This particular one came from my understanding of Big Table and the code. 

For me this works, I think of (internal) rows as roughly "containing" the CF's. 

In the CQL world it works for me as well, the partition key (first part of the primary key)
is important and identifies the storage "container" that has the columns. 

Your milage may vary
-----------------
Aaron Morton
Freelance Cassandra Developer
New Zealand

@aaronmorton
http://www.thelastpickle.com

On 31/01/2013, at 4:43 PM, Edward Capriolo <edlinuxguru@gmail.com> wrote:

> That should not bother you.
> 
> For example, if your doing an hbase scan that crosses two column families,
> that count end up being two (disk) seeks.
> 
> Having an API that hides the seeks from you does not give you better
> performance, it only helps you when your debating with people that do not
> understand the fundamentals.


Mime
View raw message