You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2011/04/29 15:18:03 UTC

[jira] [Resolved] (CASSANDRA-2122) Replace messages with a serialization framework for easy backwards compatibility

     [ https://issues.apache.org/jira/browse/CASSANDRA-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis resolved CASSANDRA-2122.
---------------------------------------

       Resolution: Won't Fix
    Fix Version/s:     (was: 1.0)

Consensus is that spending effort to make our intra-cluster messaging less flexible is not a good use of time.

> Replace messages with a serialization framework for easy backwards compatibility
> --------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-2122
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2122
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Gary Dusbabek
>              Labels: ponies
>
> CASSANDRA-1015 provided a way to keep 0.8 messages compatible with 0.7 messages.  The next step will be to replace messaging with something that is more easily backward compatible.  Avro, thrift and msgpack have all been suggested as frameworks.
> If done properly, this will amount to rewriting MessagingService, though I'm not sure that's possible at this point (we don't have backwards-compatible disk structures, and those are sent inside the RowMutations).  It may be preferred to keep MessagingService, and use it to package up messages that are serialized by whatever framework.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira