incubator-cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Murali <muralidharan....@gmail.com>
Subject Re: CQL or Thrift ?
Date Tue, 06 Aug 2013 05:55:57 GMT
Hi Aswani Kumar,
Please let me know, any specific reasons that you're recommending thrift?

Thanks
Murali.

On Tue, Aug 6, 2013 at 11:16 AM, Aswani Kumar Vonteddu <
as.wins.code@hotmail.com> wrote:

> I'd recommend Thrift.
>
> > Date: Mon, 5 Aug 2013 14:08:52 -0500
> > Subject: CQL or Thrift ?
> > From: nuliknol@gmail.com
> > To: dev@cassandra.apache.org
> >
> > Hi,
> > I need a client in C (not C++) to work with Cassandra, so since there
> > is no one yet I would do my own. So far I have checked, I can do it
> > through Thrift RPC port, or through CQL port. As I understand, CQL
> > doesn't support direct "mutate" or "get_range_slices" calls like
> > Thrift does , so being Thrift API more low level, it should be faster
> > for specific queries my application would execute. The question is,
> > what do you recommend me to use, Thrift or CQL3 native protocol?
> > Thrift API supports  CQL , but not the other way around. If commands
> > go through CQL, there will be some Java code executed and I don't know
> > which would be faster, sending the raw "mutate"s through thrift by C
> > application or executing a prepared CQL3 query by Java? I am
> > interested more in performance, rather than in easiness of use. Will
> > appreciate very much your comments.
> >
> > Nulik
>
>



-- 
Thanks,
Murali
99025-33335

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message