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?
