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 markxr@gmail.com designates
 209.85.218.217 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=sYcWsCjT2UT9YCT1syNBoStD+Ja+phnQon6ulsYUGuaNGLZt86XNeoNeBXYkipcEyr
         jUANMg+PrFIX6LHduVDhJU/QvmmUizgC066BqslXICwjDFp28fuAORfLIgv83iPCvhoV
         Ym3gaduGpmHCrpHLQeabRgG+pTp5UbfPrlMWk=
MIME-Version: 1.0
In-Reply-To: <91790a981001201303w2183182ax75afe6612ecc53d1@mail.gmail.com>
References: <91790a981001201231o6e346c2ct4fb687c7799fe431@mail.gmail.com>
	 <cdc5ad201001201256n49bd10c9ge2d1abed0ce5767c@mail.gmail.com>
	 <91790a981001201303w2183182ax75afe6612ecc53d1@mail.gmail.com>
Date: Wed, 20 Jan 2010 21:20:28 +0000
Message-ID: <ff1a07b81001201320t56c0288cpe7bf02117c9f81ba@mail.gmail.com>
Subject: Re: Cassandra to store logs as a list
From: Mark Robson <markxr@gmail.com>
To: cassandra-user@incubator.apache.org
Content-Type: multipart/alternative; boundary=0015175cd86ed4bbad047d9f27e0

--0015175cd86ed4bbad047d9f27e0
Content-Type: text/plain; charset=ISO-8859-1

I think you really want to be using the OrderPreservingPartitioner and using
time-based keys.

It depends exactly how you're querying it. All querying use-cases need to be
taken into account when deciding how to structure your data.

If you use a time-based key with OPP, typically data become very unbalanced,
because the balancing algorithm (such as exists) depends on the keys
continuing to have a similar distribution as when the nodes were
kickstarted.

One solution would be to put some other field on the beginning of the key
that you might wish to use such as account id, customer id, site id, etc, if
you have sufficient of these to spread the data out evenly (do it in hex and
zero pad it, of course)

Mark

--0015175cd86ed4bbad047d9f27e0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I think you really want to be using the OrderPreservingPartitioner and usin=
g time-based keys.<br><br>It depends exactly how you&#39;re querying it. Al=
l querying use-cases need to be taken into account when deciding how to str=
ucture your data.<br>
<br>If you use a time-based key with OPP, typically data become very unbala=
nced, because the balancing algorithm (such as exists) depends on the keys =
continuing to have a similar distribution as when the nodes were kickstarte=
d.<br>
<br>One solution would be to put some other field on the beginning of the k=
ey that you might wish to use such as account id, customer id, site id, etc=
, if you have sufficient of these to spread the data out evenly (do it in h=
ex and zero pad it, of course)<br>
<br>Mark<br>

--0015175cd86ed4bbad047d9f27e0--