incubator-cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vladimir Prudnikov <v.prudni...@gmail.com>
Subject CQL vs Thrift
Date Wed, 17 Jul 2013 20:18:02 GMT
Hi all,

This is may be is not the right place to ask, but I though developers can
answer to my questions better than users.

It looks clear that Cassandra dev team concentrates on CQL rather than
Thrift interface. I'm considering using Cassandra as a storage for my
current project which will replace MySQL. I still have problem choosing
between Thrift (Pycassa) vs CQL (cqlengine, python-driver).

Personally after using pycassa in test project I fall in love with it. I'd
prefer to use pycassa rather than python-driver, cqlengine or write raw
queries.

1) What's going on with Thrift interface and pycassa? I read somewhere that
it will be for backward compatibility, but does it mean that new features
will not be added to the Thrift interface hence will not be available with
pycassa? For example collections
http://www.datastax.com/dev/blog/cql3_collections.

2) Currently column families created using CQL is not visible through the
Thrift interface and vice versa. If I start with pycassa and in future I
decide to use CQL (due to lack of new features) will it be possible to use
these CFs? Or convert them so they become visible and accessible using CQL?

3) Also I've done some basic tests (pycassa vs. cqlengine, no prepared
statements) and seems like pycassa performs almost 2 times better which
makes it more preferable. It was simple inserts of couple thousands rows.

Do I have to put up with all this and start using CQL?

Thanks,
-- 
Vladimir Prudnikov

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