cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "T Jake Luciani (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-1015) Internal Messaging should be backwards compatible
Date Fri, 31 Dec 2010 02:22:47 GMT


T Jake Luciani commented on CASSANDRA-1015:

Johnathan, this is one approach I've had success with using thrift
So based on the type field you serialize to one of the column types.

> Internal Messaging should be backwards compatible
> -------------------------------------------------
>                 Key: CASSANDRA-1015
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Ryan King
>            Assignee: Gary Dusbabek
>            Priority: Critical
>             Fix For: 0.8
> Currently, incompatible changes in the node-to-node communication prevent rolling restarts
of clusters.
> In order to fix this we should:
> 1) use a framework that makes doing compatible changes easy
> 2) have a policy of only making compatible changes between versions n and n+1*
> * Running multiple versions should only be supported for small periods of time. Running
clusters of mixed version is not needed here.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message