[
https://issues.apache.org/jira/browse/CASSANDRA-5436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625365#comment-13625365
]
Sylvain Lebresne commented on CASSANDRA-5436:
---------------------------------------------
Actually, would you mind pull out the versioning bits from CASSANDRA-5349 and
move it there? I'd like to handle that part correctly (including forking the
doc, etc...) before starting to add too much new stuffs.
bq. it does not allow new clients to connect to old servers though
Well they can connect, they will just get a ProtocolException with "Invalid or
unsupported protocol version" :). More seriously, I'm not sure we can do much
better, new clients will have to talk the old protocol to talk to old servers.
That being say, the exception we currently throw is not as helpful as can be
because we include which version we don't speak but not which version we speak.
I don't know, maybe adding some '[supported_version=...]' to the error string
could be enough (though slightly ugly, granted).
> Binary protocol versioning
> --------------------------
>
> Key: CASSANDRA-5436
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5436
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Marcus Eriksson
>
> 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
