Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of tyler@datastax.com designates
 209.85.220.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAJ5JRqB2OX=TEkK7Vg9s-MWsdZf=+T09O9Vmcwx=Rs98C8YYfg@mail.gmail.com>
References: 
 <CAJ5JRqB2OX=TEkK7Vg9s-MWsdZf=+T09O9Vmcwx=Rs98C8YYfg@mail.gmail.com>
Date: Thu, 20 Sep 2012 22:01:04 -0500
Message-ID: 
 <CAAam9suFG8a06WojrFxVd34AsfZeQn8CYBncg2TQqT8x1cPn1A@mail.gmail.com>
Subject: Re: Should row keys be inserted in ascending order?
From: Tyler Hobbs <tyler@datastax.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=20cf3071ca1455512004ca2d738e

--20cf3071ca1455512004ca2d738e
Content-Type: text/plain; charset=ISO-8859-1

Rows are actually stored on disk in the order of the hash of their keys
when using RandomPartitioner.

Furthermore, the rows are stored in SSTables, which are immutable, and are
periodically compacted together.  There's no shifting involved.  This gives
an overview: http://wiki.apache.org/cassandra/MemtableSSTable

On Thu, Sep 20, 2012 at 7:52 PM, Cory Mintz <cory.p.mintz@gmail.com> wrote:

> The DataModel page in the Cassandra Wiki (
> http://wiki.apache.org/cassandra/DataModel) says:
>
>
>
> "In Cassandra, each column family is stored in a separate file, and the
> file is sorted in row (i.e. key) major order."
>
>
>
> Does this mean that new row keys should be ascending? If they are not
> ascending does that mean all
>
> of the data after the new key needs to be shifted down?
>
>
> Thanks.
>
> Cory
>


-- 
Tyler Hobbs
DataStax <http://datastax.com/>

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

Rows are actually stored on disk in the order of the hash of their keys whe=
n using RandomPartitioner.<br><br>Furthermore, the rows are stored in SSTab=
les, which are immutable, and are periodically compacted together.=A0 There=
&#39;s no shifting involved.=A0 This gives an overview: <a href=3D"http://w=
iki.apache.org/cassandra/MemtableSSTable">http://wiki.apache.org/cassandra/=
MemtableSSTable</a><br>
<br><div class=3D"gmail_quote">On Thu, Sep 20, 2012 at 7:52 PM, Cory Mintz =
<span dir=3D"ltr">&lt;<a href=3D"mailto:cory.p.mintz@gmail.com" target=3D"_=
blank">cory.p.mintz@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">
<p class=3D"MsoNormal">The DataModel page in the Cassandra Wiki (<a href=3D=
"http://wiki.apache.org/cassandra/DataModel" target=3D"_blank">http://wiki.=
apache.org/cassandra/DataModel</a>)
says:</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">&quot;In Cassandra, each column family is stored in =
a
separate file, and the file is sorted in row (i.e. key) major order.&quot;<=
/p>

<p class=3D"MsoNormal">=A0</p><p class=3D"MsoNormal">Does this mean that ne=
w row keys should be ascending? If they are not ascending does that mean al=
l</p><p class=3D"MsoNormal">of the data after the new key needs to be shift=
ed down?</p>

<p class=3D"MsoNormal"><br></p><p class=3D"MsoNormal">Thanks.</p><span clas=
s=3D"HOEnZb"><font color=3D"#888888"><p class=3D"MsoNormal">Cory</p>
</font></span></blockquote></div><br><br clear=3D"all"><br>-- <br><font col=
or=3D"#888888">Tyler Hobbs<span></span><br>
<a href=3D"http://datastax.com/" target=3D"_blank">DataStax</a><br></font><=
br>

--20cf3071ca1455512004ca2d738e--