On Mon, 2011-01-17 at 12:12 -0500, Jake Luciani wrote: > Some context: We have begun the process of removing Avro from the > service layer CASSANDRA-926. We currently use Avro for schema > migrations internally, and we have two open items that are using Avro > for our internal file storage. CASSANDRA-1472 and CASSANDRA-674.
FWIW, this should be done (removing the RPC interface). Anything missed is deserving of a bug report > My opinion is we need to control the lowest layers of the code and not > rely on a third party library. By using a third party library like > Avro, it becomes a black box that we need to deeply understand and > work around. Also, since Avro is developed separately we have another > core dependency that could disrupt releases (say a bug in Avro). +1 The Avro RPC interface was an experiment, and it was always the case that if it didn't supplant the Thrift interface as status quo, that it'd be removed. However, as I remember it, part of the justification for using it in migrations was that it was already there. In hindsight that was probably a mistake. Anyway, we have too many dependencies as it is, I'd rather move toward eliminating it entirely unless there is a very compelling reason not to (I don't think there is). -- Eric Evans eev...@rackspace.com
