Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of edlinuxguru@gmail.com
 designates 209.85.212.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <20130731173257.GI1764@snowy.squish.net>
References: <20130731104703.GG1764@snowy.squish.net>
	<CA+VSrLr9MUR7iF+ZUk=mwrVPP3E-Vpfvjr3MPhxZuO1d6i4wWQ@mail.gmail.com>
	<20130731173257.GI1764@snowy.squish.net>
Date: Wed, 31 Jul 2013 17:54:38 -0400
Message-ID: 
 <CAENxBwz_pPkHu3boEW0zmLm+C7An5G1ThbZN+L-sjpp41KomKw@mail.gmail.com>
Subject: Re: CQL and undefined columns
From: Edward Capriolo <edlinuxguru@gmail.com>
To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Content-Type: multipart/alternative; boundary=047d7b5d8815a798af04e2d5c5e0

--047d7b5d8815a798af04e2d5c5e0
Content-Type: text/plain; charset=ISO-8859-1

You should also profile what your data looks like on disk before picking a
format. It may not be as efficient to use one form or the other due to
extra disk overhead.


On Wed, Jul 31, 2013 at 1:32 PM, Jon Ribbens <
jon-cassandra@unequivocal.co.uk> wrote:

> On Wed, Jul 31, 2013 at 02:21:52PM +0200, Alain RODRIGUEZ wrote:
> >    I like to point to this article from Sylvain, which is really well
> >    written.
> >    http://www.datastax.com/dev/blog/thrift-to-cql3
>
> Ah, thankyou, it looks like a combination of multi-column "PRIMARY KEY"
> and use of collections may well suffice for what I want. I must admit
> that I did not find any of this particularly obvious from the CQL
> documentation.
>
> By the way, http://cassandra.apache.org/doc/cql3/CQL.html#createTableStmt
> says "A table with COMPACT STORAGE must also define at least one
> clustering key", which seems to contradict definition 2 in the
> thrift-to-cql3 document you pointed me to.
>

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

<div dir=3D"ltr">You should also profile what your data looks like on disk =
before picking a format. It may not be as efficient to use one form or the =
other due to extra disk overhead.<br></div><div class=3D"gmail_extra"><br><=
br>
<div class=3D"gmail_quote">On Wed, Jul 31, 2013 at 1:32 PM, Jon Ribbens <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:jon-cassandra@unequivocal.co.uk" targe=
t=3D"_blank">jon-cassandra@unequivocal.co.uk</a>&gt;</span> wrote:<br><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex">
On Wed, Jul 31, 2013 at 02:21:52PM +0200, Alain RODRIGUEZ wrote:<br>
&gt; =A0 =A0I like to point to this article from Sylvain, which is really w=
ell<br>
&gt; =A0 =A0written.<br>
&gt; =A0 =A0<a href=3D"http://www.datastax.com/dev/blog/thrift-to-cql3" tar=
get=3D"_blank">http://www.datastax.com/dev/blog/thrift-to-cql3</a><br>
<br>
Ah, thankyou, it looks like a combination of multi-column &quot;PRIMARY KEY=
&quot;<br>
and use of collections may well suffice for what I want. I must admit<br>
that I did not find any of this particularly obvious from the CQL<br>
documentation.<br>
<br>
By the way, <a href=3D"http://cassandra.apache.org/doc/cql3/CQL.html#create=
TableStmt" target=3D"_blank">http://cassandra.apache.org/doc/cql3/CQL.html#=
createTableStmt</a><br>
says &quot;A table with COMPACT STORAGE must also define at least one<br>
clustering key&quot;, which seems to contradict definition 2 in the<br>
thrift-to-cql3 document you pointed me to.<br>
</blockquote></div><br></div>

--047d7b5d8815a798af04e2d5c5e0--