incubator-cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Ellis <jbel...@gmail.com>
Subject Re: network compatibility from 0.6 to 0.7
Date Thu, 05 Aug 2010 15:05:58 GMT
The situation today is that network compatibility in trunk has been
broken without us noticing for a while now -- in CASSANDRA-956
(according to git annotate) we changed ColumnFamily serialization in a
non-backwards-compatible way.

Given the difficulty on the client side of mixing 0.6 and 0.7, most
sites are going to end up doing a Big Bang upgrade anyway.  So is it
really worth a lot of effort on the network protocol side?

On Thu, Jul 22, 2010 at 5:35 PM, Sylvain Lebresne <sylvain@yakaz.com> wrote:
> What would be the pros of breaking it for 0.7 now ?
> I suppose you have something specific in mind that would break
> compatibility ?
>
> On Thu, Jul 22, 2010 at 8:19 PM, Gary Dusbabek <gdusbabek@gmail.com> wrote:
>> I think this depends on how much value users place in rolling upgrades
>> (it's going to vary).
>>
>> My opinion is that we should be allowed to break it between major
>> versions if required.
>>
>> Gary.
>>
>> On Thu, Jul 22, 2010 at 11:49, Jonathan Ellis <jbellis@gmail.com> wrote:
>>> 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
>>>
>>
>



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

Mime
View raw message