incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Haddad <>
Subject Re: Choosing python client lib for Cassandra
Date Tue, 26 Nov 2013 19:21:24 GMT
We're currently using the "cql" package, which is really a wrapper around

To your concern about deadlines, I'm not sure how writing raw CQL is going
to be any faster than using a mapper library for anything other than the
most trivial of project.

On Tue, Nov 26, 2013 at 11:09 AM, Kumar Ranjan <> wrote:

> Jon - Thanks. As I understand, cqlengine is an object mapper and must be
> using for cql prepare statements. What are you wrapping it with, in
> alternative to python-driver?
> —
> Sent from Mailbox <> for iPhone
> On Tue, Nov 26, 2013 at 1:19 PM, Jonathan Haddad <>wrote:
>>  So, for cqlengine (, we're
>> currently using the thrift api to execute CQL until the native driver is
>> out of beta.  I'm a little biased in recommending it, since I'm one of the
>> primary authors.  If you've got cqlengine specific questions, head to the
>> mailing list:!forum/cqlengine-users
>> If you want to roll your own solution, it might make sense to take an
>> approach like we did and throw a layer on top of thrift so you don't have
>> to do a massive rewrite of your entire app once you want to go native.
>> Jon
>> On Tue, Nov 26, 2013 at 9:46 AM, Kumar Ranjan <>wrote:
>>>  I have worked with Pycassa before and wrote a wrapper to use batch
>>> mutation & connection pooling etc. But
>>> recommends now to use
>>> CQL 3 based api because Thrift based api (Pycassa) will be supported for
>>> backward compatibility only. Apache site recommends to use Python api
>>> written by DataStax which is still in Beta (As per their documentation).
>>> See warnings from their python-driver/README.rst file
>>> *Warning*
>>> This driver is currently under heavy development, so the API and layout
>>> of packages,modules, classes, and functions are subject to change. There
>>> may also be serious bugs, so usage in a production environment is *not* recommended
>>> at this time.
>>> DataStax site recommends
>>> using DB-API 2.0 plus legacy api's. Is there more? Has any one compared
>>> between CQL 3 based apis? Which stands out on top? Answers based on facts
>>> will help the community so please refrain from opinions.
>>> Please help ??
>> --
>> Jon Haddad
>> skype: rustyrazorblade

Jon Haddad
skype: rustyrazorblade

View raw message