[
https://issues.apache.org/jira/browse/CASSANDRA-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933582#action_12933582
]
Gary Dusbabek commented on CASSANDRA-1015:
------------------------------------------
bq. I think this would defeat the purpose of using a ser/de framework:
How? we're using it for serialization. That's less code we have to write.
Nothing is going to protect us from the kind of format changes we are prone to
making. I don't see this practice changing as it is usually the result of
coming up with a better way to do things and not just the desire of slipping a
new field into/out-of a message type.
bq. additionally, generating record objects for this arrangement would be a
nightmare.
I disagree. I can't understand how this would be hard. Messages rarely change
from version to version, so there wouldn't be a lot of work to begin with.
When things do change, you a) remove the oldest format, b) add the newer
format, c) update the translator.
> 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.
