I use both Thrift and CQL. my bias take is use CQL for select queries and thrift for insert/update. I like being able to insert exactly the data type I want for the column name and value. CQL is more user friendly, but it lacks the flexibility of thrift in terms of using different data types for column names and values.
the SQL metaphor only goes so far. My bias opinion, you're not getting the most out of Cassandra if you're only using CQL. On Thu, Jan 24, 2013 at 6:38 PM, Aaron Turner <[email protected]> wrote: > Either CQL or a higher level API running on top of Thrift like > Hector/Asyntax/etc. > > Thrift is uh... painful. > > On Thu, Jan 24, 2013 at 3:35 PM, Matthew Langton <[email protected]> wrote: >> Hi all, >> >> I started looking at Cassandra awhile ago and got used to the Thrift API. I >> put it on the back burner for awhile though until now. To get back up to >> speed I have read a lot of documentation at the DataStax website, and it >> appears that the Thrift API is no longer considered the ideal way to >> interface with Cassandra. >> >> So my questions are these: >> >> What is the future of the Thrift API, should I just ignore it going forward >> and use CQL? >> >> If CQL is the preferred way to interface with Cassandra, does using any of >> the clients listed here: http://wiki.apache.org/cassandra/ClientOptions >> provide me any benefits over using a JDBC like the one listed here >> http://code.google.com/a/apache-extras.org/p/cassandra-jdbc/ >> >> Thanks, >> Matt >> >> > > > > -- > Aaron Turner > http://synfin.net/ Twitter: @synfinatic > http://tcpreplay.synfin.net/ - Pcap editing and replay tools for Unix & > Windows > Those who would give up essential Liberty, to purchase a little temporary > Safety, deserve neither Liberty nor Safety. > -- Benjamin Franklin > "carpe diem quam minimum credula postero"
