incubator-cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stu Hood" <stu.h...@rackspace.com>
Subject RE: network compatibility from 0.6 to 0.7
Date Thu, 22 Jul 2010 17:39:18 GMT
> So I think we should probably try to preserve compatibility in 0.7.
We could probably limit the scope of our network compatibility to "steady-state" messages,
aka, nothing having to do with bootstrap, repair, etc.

-----Original Message-----
From: "Stu Hood" <stu.hood@rackspace.com>
Sent: Thursday, July 22, 2010 12:35pm
To: dev@cassandra.apache.org
Subject: RE: network compatibility from 0.6 to 0.7

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.

So I think we should probably try to preserve compatibility in 0.7.


-----Original Message-----
From: "Jonathan Ellis" <jbellis@gmail.com>
Sent: Thursday, July 22, 2010 11:49am
To: cassandra-dev@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)

-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of Riptano, the source for professional Cassandra support
http://riptano.com





Mime
View raw message