On Thu, 2010-07-22 at 12:35 -0500, Stu Hood wrote: > I feel like the next time we break network compatibility should be the > last time, aka, the release when we introduce a backwards compatible > RPC layer (Avro?), and implement support for dropping messages that a > node can't handle.
Yeah, I think a full cluster restart is the worst upgrade hurdle that we currently impose on users, and I wouldn't like to see us do it more than one last time. > So I think we should probably try to preserve compatibility in 0.7. It seems a little late to get it right for 0.7, so I agree. > -----Original Message----- > From: "Jonathan Ellis" <jbel...@gmail.com> > Sent: Thursday, July 22, 2010 11:49am > To: cassandra-...@incubator.apache.org > Subject: network compatibility from 0.6 to 0.7 > > How useful is this to insist on, given that 0.7 thrift api is fairly > incompatible with 0.6's? (timestamp -> Clock change being the biggest > problem there) -- Eric Evans eev...@rackspace.com
