Mailing-List: contact cassandra-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cassandra-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of jbellis@gmail.com designates
 74.125.82.47 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=H7wadFVNJwYZUIcIwxoTrkvtni7slaXdOreBQ4MJL99VPUhfcLbbaTkOgbq5PkiiRq
         zoa46/fVDh3vsZK6V4Gz2C6WF16vWLoZY0BCUJgE8S9+WZxg8eSuOXlBYMbaxh6OKmJG
         VQ5NHd/kKrBxsqFuUhaRE3bffSmvm/1F+9MCs=
MIME-Version: 1.0
In-Reply-To: <EF62FAEA-DA87-4306-9B84-7A45751F080D@nokia.com>
References: <EF62FAEA-DA87-4306-9B84-7A45751F080D@nokia.com>
From: Jonathan Ellis <jbellis@gmail.com>
Date: Tue, 2 Mar 2010 16:17:31 -0600
Message-ID: <e06563881003021417j25c09ca3y43aa58e546cef030@mail.gmail.com>
Subject: Re: Index values: data or pointers?
To: cassandra-user@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Mar 2, 2010 at 4:13 PM,  <Jeremey.Barrett@nokia.com> wrote:
> I'm exploring data layouts and it seems like the common practice is to st=
ore an index in one CF (e.g. userid for row key and thingid for column name=
) and then to fetch all the things by their thingids separately... so get i=
ndex, and then get each key in the index.
>
> If a thing changes relatively infrequently but gets read often, seems lik=
e it would be more performant (especially with writes being very fast) to j=
ust stuff whole objects into indexes rather than simply ids. A "whole objec=
t" could be a JSON object or a serialized class or who knows what.

Yes.  This is one place supercolumns can be very useful, since it
allows doing this w/o nasty hacks like you mention. :)

-Jonathan