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 woolfel@gmail.com designates
 209.85.220.178 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <61E7EDCF-0F8D-4C4C-8D35-DF7808B24136@jonhaddad.com>
References: 
 <CANJo1uA6_-SEQ1Qu-CB89aahpEYuDYe_-Q-Q3X725TY8Qsyf4w@mail.gmail.com>
	<61E7EDCF-0F8D-4C4C-8D35-DF7808B24136@jonhaddad.com>
Date: Fri, 30 Aug 2013 13:53:54 -0400
Message-ID: 
 <CAKv2g8emby9j5rBX20ty3EawmRY2=K2mmMTyfkXPiq+whxAuOw@mail.gmail.com>
Subject: Re: CQL & Thrift
From: Peter Lin <woolfel@gmail.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=bcaec5016229eb7ff904e52de7db

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

my bias perspective, I find the sweet spot is thrift for insert/update and
CQL for select queries.

CQL is too limiting and negates the power of storing arbitrary data types
in dynamic columns.


On Fri, Aug 30, 2013 at 1:45 PM, Jon Haddad <jon@jonhaddad.com> wrote:

> If you're going to work with CQL, work with CQL.  If you're going to work
> with Thrift, work with Thrift.  Don't mix.
>
> On Aug 30, 2013, at 10:38 AM, Vivek Mishra <mishra.vivs@gmail.com> wrote:
>
> Hi,
> If i a create a table with CQL3 as
>
> create table user(user_id text PRIMARY KEY, first_name text, last_name
> text, emailid text);
>
> and create index as:
> create index on user(first_name);
>
> then inserted some data as:
> insert into user(user_id,first_name,last_name,"emailId")
> values('@mevivs','vivek','mishra','vivek.mishra@impetus.co.in');
>
>
> Then if update same column family using Cassandra-cli as:
>
> update column family user with key_validation_class='UTF8Type' and
> column_metadata=[{column_name:last_name, validation_class:'UTF8Type',
> index_type:KEYS},{column_name:first_name, validation_class:'UTF8Type',
> index_type:KEYS}];
>
>
> Now if i connect via cqlsh and explore user table, i can see column
> first_name,last_name are not part of table structure anymore. Here is the
> output:
>
> CREATE TABLE user (
>   key text PRIMARY KEY
> ) WITH
>   bloom_filter_fp_chance=0.010000 AND
>   caching='KEYS_ONLY' AND
>   comment='' AND
>   dclocal_read_repair_chance=0.000000 AND
>   gc_grace_seconds=864000 AND
>   read_repair_chance=0.100000 AND
>   replicate_on_write='true' AND
>   populate_io_cache_on_flush='false' AND
>   compaction={'class': 'SizeTieredCompactionStrategy'} AND
>   compression={'sstable_compression': 'SnappyCompressor'};
>
> cqlsh:cql3usage> select * from user;
>
>  user_id
> ---------
>  @mevivs
>
>
>
>
>
> I understand that, CQL3 and thrift interoperability is an issue. But this
> looks to me a very basic scenario.
>
>
>
> Any suggestions? Or If anybody can explain a reason behind this?
>
> -Vivek
>
>
>
>
>
>

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

<div dir=3D"ltr"><div><div><br></div>my bias perspective, I find the sweet =
spot is thrift for insert/update and CQL for select queries.<br><br></div>C=
QL is too limiting and negates the power of storing arbitrary data types in=
 dynamic columns.<br>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Fri,=
 Aug 30, 2013 at 1:45 PM, Jon Haddad <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:jon@jonhaddad.com" target=3D"_blank">jon@jonhaddad.com</a>&gt;</span> wro=
te:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word"><div>If =
you&#39;re going to work with CQL, work with CQL. =A0If you&#39;re going to=
 work with Thrift, work with Thrift. =A0Don&#39;t mix.</div>
<div><div class=3D"h5"><br><div><div>On Aug 30, 2013, at 10:38 AM, Vivek Mi=
shra &lt;<a href=3D"mailto:mishra.vivs@gmail.com" target=3D"_blank">mishra.=
vivs@gmail.com</a>&gt; wrote:</div><br><blockquote type=3D"cite"><div dir=
=3D"ltr">
Hi,<div>If i a create a table with CQL3 as=A0</div><div><div><br></div><div=
>create table user(user_id text PRIMARY KEY, first_name text, last_name tex=
t, emailid text);</div><div><br></div><div>
and create index as:</div><div><div>create index on user(first_name);</div>=
<div><br></div><div>then inserted some data as:</div><div>insert into user(=
user_id,first_name,last_name,&quot;emailId&quot;) values(&#39;@mevivs&#39;,=
&#39;vivek&#39;,&#39;mishra&#39;,&#39;<a href=3D"mailto:vivek.mishra@impetu=
s.co.in" target=3D"_blank">vivek.mishra@impetus.co.in</a>&#39;);<br>

</div><div><br></div><div><br></div><div>Then if update same column family =
using Cassandra-cli as:</div><div><br></div><div>update column family user =
with key_validation_class=3D&#39;UTF8Type&#39; and column_metadata=3D[{colu=
mn_name:last_name, validation_class:&#39;UTF8Type&#39;, index_type:KEYS},{c=
olumn_name:first_name, validation_class:&#39;UTF8Type&#39;, index_type:KEYS=
}];<br>

</div><div><br></div><div><br></div><div>Now if i connect via cqlsh and exp=
lore user table, i can see column first_name,last_name are not part of tabl=
e structure anymore. Here is the output:</div><div>
<br></div><div><div>CREATE TABLE user (</div><div>=A0 key text PRIMARY KEY<=
/div><div>) WITH</div><div>=A0 bloom_filter_fp_chance=3D0.010000 AND</div><=
div>=A0 caching=3D&#39;KEYS_ONLY&#39; AND</div><div>=A0 comment=3D&#39;&#39=
; AND</div>

<div>=A0 dclocal_read_repair_chance=3D0.000000 AND</div><div>=A0 gc_grace_s=
econds=3D864000 AND</div><div>=A0 read_repair_chance=3D0.100000 AND</div><d=
iv>=A0 replicate_on_write=3D&#39;true&#39; AND</div><div>=A0 populate_io_ca=
che_on_flush=3D&#39;false&#39; AND</div>

<div>=A0 compaction=3D{&#39;class&#39;: &#39;SizeTieredCompactionStrategy&#=
39;} AND</div><div>=A0 compression=3D{&#39;sstable_compression&#39;: &#39;S=
nappyCompressor&#39;};</div><div><br></div><div>cqlsh:cql3usage&gt; select =
* from user;</div>

<div><br></div><div>=A0user_id</div><div>---------</div><div>=A0@mevivs</di=
v><div><br></div></div><div><br></div><div><br></div><div><br></div><div><b=
r></div><div>I understand that, CQL3 and thrift interoperability is an issu=
e. But this looks to me a very basic scenario.</div>

<div><br></div><div><br></div><div><br></div><div>Any suggestions? Or If an=
ybody can explain a reason behind this?</div><div><br></div><div>-Vivek</di=
v><div><br></div><div><br>
</div><div><br></div></div><div><br></div></div></div>
</blockquote></div><br></div></div></div></blockquote></div><br></div>

--bcaec5016229eb7ff904e52de7db--