Just curious. Since the CQL will be the future of Cassandra client access interface.
And then I only need to develop one set of database access code. DRY(single piece of knowledge)
Thanks,
Charlie | DBA
Just curious. Since the CQL will be the future of Cassandra client access interface.
And then I only need to develop one set of database access code. DRY(single piece of knowledge)
Thanks,
Charlie | DBA
Pycassa's goal is to support an OO-based API. It will probably move to CQL eventually for ease of development but that is an implementation detail. We're not in a hurry.
Charlie- you might want to start with python-cql instead of pycassa if you want to do CQL instead of the pycassa interface. But the pycassa interface probably won't be changing, so you could keep using that and still achieve your DRY goal.
Hi thepaul,
Do you mean below drivers?
http://pypi.python.org/pypi/cql/1.0.10
and
http://code.google.com/a/apache-extras.org/p/cassandra-dbapi2/
Thanks and have a successful day!
Charlie | DBA
Charlie- yep, that's the one! The source is at Google Code, but it's also hosted on PyPI for ease of installation.
From what I know, DB-API 2.0 compliant client library for Cassandra/CQL, doesn't support connection pooling load balance advance features.
connection pool is a necessary feature for multi-user production application.
Thanks,
Charlie | DBA developer
What does exactly mean "doesn't support connection pooling load balance advance features"? Could you be a bit more specific?
You must log in to post.