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: local policy includes SPF record at
 spf.trusted-forwarder.org)
MIME-Version: 1.0
In-Reply-To: 
 <CAKv2g8eUA4Uen5tV0L56zqXtThB+GXfdNYMrvOCSR_Yd-K=R0g@mail.gmail.com>
References: 
 <CAB9JMRfcMAdKg6s=Bq-+enMR405WFP-GVvvBoi-m5hTtJi0L5w@mail.gmail.com>
	<CAKv2g8eUA4Uen5tV0L56zqXtThB+GXfdNYMrvOCSR_Yd-K=R0g@mail.gmail.com>
Date: Tue, 17 Dec 2013 14:08:51 +0000
Message-ID: 
 <CADptzMkY3T+ZcqO2ZYn7RkK=JwXO1BV4wMW15at8JXcQSdp_+w@mail.gmail.com>
Subject: Re: Why was Thrift defined obsolete?
From: Stuart Broad <stuart@moogsoft.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=047d7bacb4d6d7d67204edbb7716

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

Hopefully this is a valid clarification, rather than a hijack of your
thread!

How does the binary protocol fit into this?  I have not used it but was
told you can implement CQL calls via thrift or via the binary protocol.  Is
the binary protocol superior to thrift?

If you use the binary protocol do you have to use CQL?

Cheers,

Stuart
 On 17 Dec 2013 14:01, "Peter Lin" <woolfel@gmail.com> wrote:

>
> That's just mis-information by people that don't understand thrift.
>
> The thrift drivers are still much more mature than the java drivers right
> now. DataStax has stated on multiple occasions thrift isn't going any
> where. CQL is fine if people only want to use SQL-like language. Search the
> cassandra mailing list and you'll see this topic comes up regularly.
>
> My bias perspective is "use thrift" to use 100% of the features that
> Cassandra provides, or use pure CQL and limit yourself to 90%.
>
> The main downside of using pure CQL (ie no thrift) is that once you've
> defined a default type for column values, you can't stick arbitrary data
> into dynamic columns. Cassandra will tell you when you try to insert a Date
> when the default value type is int. Basically, it will throw an exception.
> In contrast, if you use thrift, you can insert what ever type you want and
> have total control over what goes into dynamic columns.
>
> For me, the biggest value of dynamic columns + data types is that I can
> insert what ever I want into dynamic columns and still have the safety net
> of knowing the type. A lot of people are afraid of thrift and don't want to
> dive deep, which is fine. I prefer to understand things at a deep level,
> and use a tool to the fullest extent.
>
> peter
>
>
> On Tue, Dec 17, 2013 at 8:40 AM, Daneel Yaitskov <rtfm.rtfm.rtfm@gmail.com
> > wrote:
>
>> Hi,
>>
>> I've read some articles about Cassandra and I noticed an opinion that
>> Thrift protocol
>> has some flaws. Thrift should go away in the nearest futures.
>>
>> But I cannot find any reference answering the question why is it so bad?
>>
>>
>> --
>> Daneel S. Yaitskov
>>
>
>

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

<p dir=3D"ltr">Hopefully this is a valid clarification, rather than a hijac=
k of your thread!</p>
<p dir=3D"ltr">How does the binary protocol fit into this?=A0 I have not us=
ed it but was told you can implement CQL calls via thrift or via the binary=
 protocol.=A0 Is the binary protocol superior to thrift?</p>
<p dir=3D"ltr">If you use the binary protocol do you have to use CQL?</p>
<p dir=3D"ltr">Cheers,</p>
<p dir=3D"ltr">Stuart<br>
</p>
<div class=3D"gmail_quote">On 17 Dec 2013 14:01, &quot;Peter Lin&quot; &lt;=
<a href=3D"mailto:woolfel@gmail.com">woolfel@gmail.com</a>&gt; wrote:<br ty=
pe=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr"><div><div><div><div><div><br></div>That&#39;s just mis-inf=
ormation by people that don&#39;t understand thrift.<br><br></div>The thrif=
t drivers are still much more mature than the java drivers right now. DataS=
tax has stated on multiple occasions thrift isn&#39;t going any where. CQL =
is fine if people only want to use SQL-like language. Search the cassandra =
mailing list and you&#39;ll see this topic comes up regularly.<br>

<br></div>My bias perspective is &quot;use thrift&quot; to use 100% of the =
features that Cassandra provides, or use pure CQL and limit yourself to 90%=
.<br><br></div>The main downside of using pure CQL (ie no thrift) is that o=
nce you&#39;ve defined a default type for column values, you can&#39;t stic=
k arbitrary data into dynamic columns. Cassandra will tell you when you try=
 to insert a Date when the default value type is int. Basically, it will th=
row an exception. In contrast, if you use thrift, you can insert what ever =
type you want and have total control over what goes into dynamic columns.<b=
r>

<br></div>For me, the biggest value of dynamic columns + data types is that=
 I can insert what ever I want into dynamic columns and still have the safe=
ty net of knowing the type. A lot of people are afraid of thrift and don=
9;t want to dive deep, which is fine. I prefer to understand things at a de=
ep level, and use a tool to the fullest extent.<br>

<br>peter<br></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_q=
uote">On Tue, Dec 17, 2013 at 8:40 AM, Daneel Yaitskov <span dir=3D"ltr">&l=
t;<a href=3D"mailto:rtfm.rtfm.rtfm@gmail.com" target=3D"_blank">rtfm.rtfm.r=
tfm@gmail.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>Hi,<br><br></div><div>=
I&#39;ve read some articles about Cassandra and I noticed an opinion that T=
hrift protocol<br>

</div><div>has some flaws. Thrift should go away in the nearest futures.<br=
><br></div><div>
But I cannot find any reference answering the question why is it so bad?<sp=
an><font color=3D"#888888"><br></font></span></div><span><font color=3D"#88=
8888"><br><div><br>-- <br>Daneel S. Yaitskov<br>
</div>
</font></span></div>
</blockquote></div><br></div>
</blockquote></div>

--047d7bacb4d6d7d67204edbb7716--