It's interesting to note that in Eben Hewitt's - The definitive guide to Cassandra he states the following;
*Avro Summary* As of Cassandra version 0.7, Avro is the RPC and data serialization mechanism for Cassandra. It generates code that remote clients can use to interact with the database. It’s well-supported in the community and has the strength of growing out of the larger and very well-known Hadoop project. It should serve Cassandra well for the foreseeable future. Personally I'm pretty much married to thrift as it's used all the way through my application stack, and having played with Avro it really didn't merit the effort to move over (for me at least). How are you thinking of creating an 'application specific' transport ? --Jools On 22 December 2010 17:00, Eric Evans <eev...@rackspace.com> wrote: > > So, Avro RPC. Is anyone using this? Is there anyone interested in > seeing it maintained? > > I'm concentrating on CQL[1][2], which for me will culminate in the > creation of a new, application-specific transport, one that doesn't use > either of the frameworks. To me, the existing RPC framework is just > something to piggy-back on until things are otherwise working, and I'm > starting to think Thrift might be a better piggy here (read: it has more > momentum). > > TTBMK, the Avro RPC interface seems to be "mostly" working at present, > but it's already looking a bit like the proverbial red headed stepchild. > Or am I wrong and there are people who care deeply about this? > > > [1]: http://article.gmane.org/gmane.comp.db.cassandra.devel/2370 > [2]: https://issues.apache.org/jira/browse/CASSANDRA-1703 > > -- > Eric Evans > eev...@rackspace.com > >
