On Wed, 2010-12-22 at 17:27 +0000, Jools wrote: > 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.
Huh. That's just... wrong. > 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? Not sure what you mean, by "how" here. I haven't written a spec yet, if that's what you mean. -- Eric Evans eev...@rackspace.com
