cassandra-client-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nick Telford <nick.telf...@gmail.com>
Subject Re: Avro without ColumnOrSuperColumn?
Date Wed, 01 Sep 2010 16:31:08 GMT
Hi Jeremy,

I believe CoSC only exists because Thrift cannot handle inheritance? If avro
does, then surely it would make sense to diverge from the Thrift API in
order to create something a little easier to work with.

Regards,

Nick Telford

On 1 September 2010 15:52, Jeremy Hanna <jeremy.hanna1234@gmail.com> wrote:

> We're doing some work today to help Avro implementation along and the topic
> of ColumnOrSuperColumn came up.
>
> Would people be happy or sad if Avro didn't have the ColumnOrSuperColumn
> and instead had two different classes for that purpose?  Then in whatever
> language you would cast an object to either Column or SuperColumn.
>
> That is, would it help or hinder client development to diverge between Avro
> and Thrift in that way?

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message