My bias opinion, just because some member of cassandra develop want to abandon Thrift, I see benefits of continuing to improve it.
The great thing about open source is that as long as some people want to keep working on it and improve it, it can happen. I plan to do my best to keep Thrift going, since it gives me fine grain control that I want and need. If the ultimate goal of Cassandra is to be "as close to SQL" as practical, my bias take is use a NewSQL database that gives you the full power of subqueries, like, exists and disjunction. When customers ask me which database to choose and they really want Relational model, I tell them use NewSql. I love that Cassandra sits between NoSql and NewSql. There are things I do in Cassandra today that are much harder in NewSql or NoSql document databases. NewSql database can scale to similar sizes, so the "big" part of big data won't be a significant advantage forever. Looking at some of the recent NewSql performance numbers, it's clear the gap is closing. peter On Tue, Mar 11, 2014 at 3:59 PM, Tyler Hobbs <ty...@datastax.com> wrote: > > On Tue, Mar 11, 2014 at 2:41 PM, Shao-Chuan Wang < > shaochuan.w...@bloomreach.com> wrote: > >> >> So, does anyone know how to do "describing the splits" and "describing >> the local rings" using native protocol? >> > > For a ring description, you would do something like "select peer, tokens > from system.peers". I'm not sure about describe_splits(). > > >> >> Also, cqlsh uses python client, which is talking via thrift protocol too. >> Does it mean that it will be migrated to native protocol soon as well? >> > > Yes: https://issues.apache.org/jira/browse/CASSANDRA-6307 > > > -- > Tyler Hobbs > DataStax <http://datastax.com/> >
