Yes, this is what I am worrying about.
2011/8/24 Ryan King r...@twitter.com
On Tue, Aug 23, 2011 at 10:03 AM, Alvin UW alvi...@gmail.com wrote:
Hello,
As mentioned by Ed Anuff in his blog and slides, one way to build
customized
secondary index is:
We use one CF, each row to represent
How many unique last names do you anticipate having? How many characters in
the last name do you anticipate keeping in your index? You can easily do
the math to figure out how many you could fit on a node. I think you'll
find that the ceiling might be quite a bit higher than you think. If you
, 2011 12:48:49 PM
Subject: Re: Customized Secondary Index Schema
How many unique last names do you anticipate having? How many characters in the
last name do you anticipate keeping in your index? You can easily do the math
to figure out how many you could fit on a node. I think you'll find
name. This will ensure that your index is evenly
distributed throughout your cluster.
- Original Message -
From: Ed Anuff e...@anuff.com
To: user@cassandra.apache.org
Sent: Thursday, August 25, 2011 12:48:49 PM
Subject: Re: Customized Secondary Index Schema
How many unique last names
the matching main column family
key as the column name. This will ensure that your index is evenly
distributed throughout your cluster.
- Original Message -
From: Ed Anuff e...@anuff.com
To: user@cassandra.apache.org
Sent: Thursday, August 25, 2011 12:48:49 PM
Subject: Re: Customized Secondary
be read together. If you are going
to query for all of them at the same time anyways, this disadvantage does not
apply to you.
- Original Message -
From: Alvin UW alvi...@gmail.com
To: user@cassandra.apache.org
Sent: Thursday, August 25, 2011 5:11:07 PM
Subject: Re: Customized Secondary Index
IMHO it's only a scalability problem if those nodes have trouble handling the
throughput. The load will go all all replicas, not one, unless you turn off
Read Repair.
If it is a problem then you could manually partition the index into multiple
rows, bit of a pain thought. I'd wait and see, or
Thanks.
2011/8/24 aaron morton aa...@thelastpickle.com
IMHO it's only a scalability problem if those nodes have trouble handling
the throughput. The load will go all all replicas, not one, unless you turn
off Read Repair.
If it is a problem then you could manually partition the index into
On Tue, Aug 23, 2011 at 10:03 AM, Alvin UW alvi...@gmail.com wrote:
Hello,
As mentioned by Ed Anuff in his blog and slides, one way to build customized
secondary index is:
We use one CF, each row to represent a secondary index, with the secondary
index name as row key.
For example,
Hello,
As mentioned by Ed Anuff in his blog and slides, one way to build customized
secondary index is:
We use one CF, each row to represent a secondary index, with the secondary
index name as row key.
For example,
Indexes = {
User_Keys_By_Last_Name : {
adams : e5d61f2b-…,
alden : e80a17ba-…,
10 matches
Mail list logo
