cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5436) Binary protocol versioning
Date Mon, 08 Apr 2013 21:11:17 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-5436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625816#comment-13625816
] 

Marcus Eriksson commented on CASSANDRA-5436:
--------------------------------------------

i think we could allow new clients to talk to old servers by letting the server tell the client
what version it is. 

Now the client sends a StartupMessage, and if that has the wrong version, we just disconnect,
would perhaps be nice if the server ignored this version if it is higher than what it supports
and replies with a Ready/Authenticate-message with CURRENT_VERSION, just to allow clients
to adapt for the rest of the communication.

Might be adding a bunch of unnecessary complexity though 
                
> Binary protocol versioning
> --------------------------
>
>                 Key: CASSANDRA-5436
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5436
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Marcus Eriksson
>         Attachments: 0001-CASSANDRA-5436.patch
>
>
> There should be a way to version the binary protocol, CASSANDRA-5349 adds a message that
breaks compatibility (QueryMessage) and the ticket half-handles versioning - it allows old
clients to connect and execute queries (by always replying in the same version as the message
sent by the client), it does not allow new clients to connect to old servers though.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message