[
https://issues.apache.org/jira/browse/CASSANDRA-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933578#action_12933578
]
Stu Hood commented on CASSANDRA-1015:
-------------------------------------
> messages could basically become wrappers for a union of up to two
> sub-messages (current version and old version)
I think this would defeat the purpose of using a ser/de framework:
additionally, generating record objects for this arrangement would be a
nightmare.
> then we should use the fastest one we're incorporating
All of our alternatives are within an order of magnitude for ser/de speed
[1]... IMO, ease of use and continued support should be the main deciding
factors.
[1] https://github.com/eishay/jvm-serializers/wiki/
> 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.
