[
https://issues.apache.org/jira/browse/CASSANDRA-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933568#action_12933568
]
Gary Dusbabek commented on CASSANDRA-1015:
------------------------------------------
Stu and Ryan: thanks for the feedback.
I'm fine with using avro/thrift for serialization.
To cope with the practice of drastically changing our messages, messages could
basically become wrappers for a union of up to two sub-messages (current
version and old version). We would then need to come up with the glue to
convert between sub-message types.
I feel strongly that we should handle the conversions between message versions
and not rely on Avro/Thrift.
> Internal Messaging should be backwards compatible
> -------------------------------------------------
>
> Key: CASSANDRA-1015
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1015
> 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.
