Mailing-List: contact dev-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Subject: RE: network compatibility from 0.6 to 0.7
From: Eric Evans <eevans@rackspace.com>
To: dev@cassandra.apache.org
In-Reply-To: <1279820147.512524506@192.168.2.227>
References: <AANLkTinu-jAv7KuJHHddf2Q5ramO_jvAS_1vsROS5kSX@mail.gmail.com>
	 <1279820147.512524506@192.168.2.227>
Content-Type: text/plain; charset="UTF-8"
Date: Thu, 22 Jul 2010 16:07:16 -0700
Message-ID: <1279840036.12960.69.camel@erebus.lan>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

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" <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) 

-- 
Eric Evans
eevans@rackspace.com