Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D9F8E779E for ; Tue, 23 Aug 2011 17:04:29 +0000 (UTC) Received: (qmail 53063 invoked by uid 500); 23 Aug 2011 17:04:27 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 52978 invoked by uid 500); 23 Aug 2011 17:04:26 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 52970 invoked by uid 99); 23 Aug 2011 17:04:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Aug 2011 17:04:26 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of alvinuw@gmail.com designates 209.85.213.44 as permitted sender) Received: from [209.85.213.44] (HELO mail-yw0-f44.google.com) (209.85.213.44) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Aug 2011 17:04:20 +0000 Received: by ywe9 with SMTP id 9so288348ywe.31 for ; Tue, 23 Aug 2011 10:03:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=UJpqOQ6oMA56Ym5s97gkNDkB1drTVaG8dYwjB7NT8QQ=; b=a7tOOpCNJlAmsuiMjIzB4h6CiC7WkoYnY1jBLI76Gs29AORfLiJ4gp4Hkb5RJtFVKa 39sHr31duJLLhpoE/4+7PEpp5x/UvoeefcPMmgMtJKVWEApwa59wk4N2gjcWDWcH0Iuo CVHABegz/n+C0D8a8nIa4IMq4SKCJ7U1oKa2s= MIME-Version: 1.0 Received: by 10.142.50.15 with SMTP id x15mr2116654wfx.103.1314119039112; Tue, 23 Aug 2011 10:03:59 -0700 (PDT) Received: by 10.142.139.7 with HTTP; Tue, 23 Aug 2011 10:03:59 -0700 (PDT) Date: Tue, 23 Aug 2011 13:03:59 -0400 Message-ID: Subject: Customized Secondary Index Schema From: Alvin UW To: user Content-Type: multipart/alternative; boundary=000e0cd2e75684d74504ab2f2ee6 --000e0cd2e75684d74504ab2f2ee6 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hello, As mentioned by Ed Anuff in his blog and slides, one way to build customize= d 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 =3D { "User_Keys_By_Last_Name" : { "adams" : "e5d61f2b-=85", "alden" : "e80a17ba-=85", "anderson" : "e5d61f2b-=85", "davis" : "e719962b-=85", "doe" : "e78ece0f-=85", "franks" : "e66afd40-=85", =85 : =85, } } But the whole secondary index is partitioned into a single node, because of the row key. All the queries against this secondary index will go to this node. Of course, there are some replica nodes. Do you think this is a scalability problem, or any better solution to solve it? Thanks. --000e0cd2e75684d74504ab2f2ee6 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hello,

As mentioned by Ed Anuff in his blog and slides, one way to b= uild customized secondary index is:
We use one CF, each row to represent= a secondary index, with the secondary index name as row key.
For exampl= e,

Indexes =3D {
"User_Keys_By_Last_Name" : {
"adams&= quot; : "e5d61f2b-=85",
"alden" : "e80a17ba-=85= ",
"anderson" : "e5d61f2b-=85",
"davis&= quot; : "e719962b-=85",
"doe" : "e78ece0f-=85",
"franks" : "e= 66afd40-=85",
=85 : =85,
}
}

But the whole secondary i= ndex is partitioned into a single node, because of the row key.
All the = queries against this secondary index will go to this node. Of course, there= are some replica nodes.

Do you think this is a scalability problem, or any better solution to s= olve it?
Thanks.




--000e0cd2e75684d74504ab2f2ee6--