[
https://issues.apache.org/jira/browse/CASSANDRA-12142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15386597#comment-15386597
]
Tyler Hobbs commented on CASSANDRA-12142:
-----------------------------------------
bq. If the connection is established with an incorrect version (let’s say 42)
by the client, should the server still respond with 42? Or should it respond
with the CURRENT_VERSION?
If it's too low, we want to try to respond (sending a protocol error message)
with the version that the driver connected with. (I just fixed this in
CASSANDRA-11464.) If it's too high, we should respond with a protocol error
message with {{CURRENT_VERSION}}, as we can't correctly respond with a higher
version.
bq. The problem on the server side is that version is set for `connection`, not
for `channel` and connection is only initialised later, which means that server
would respond with CURRENT_VERSION.
I think this behavior is okay when the requested protocol version is higher
than {{CURRENT_VERSION}}, but perhaps I'm missing the problem?
> Add "beta" version native protocol flag
> ---------------------------------------
>
> Key: CASSANDRA-12142
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12142
> Project: Cassandra
> Issue Type: Sub-task
> Components: CQL
> Reporter: Tyler Hobbs
> Assignee: Alex Petrov
> Labels: protocolv5
>
> As discussed in CASSANDRA-10786, we'd like to add a new flag to the native
> protocol to allow drivers to connect using a "beta" native protocol version.
> This would be used for native protocol versions that are still in development
> and may not have all of the final features. Without the "beta" flag, drivers
> will be prevented from using the protocol version.
> This is primarily useful for driver authors to start work against a new
> protocol version when the work on that spans multiple releases. Users would
> not generally be expected to utilize this flag, although it could potentially
> be used to offer early feedback on new protocol features.
> It seems like the {{STARTUP}} message body is the best place for the new beta
> flag. We may also considering adding protocol information to the
> {{SUPPORTED}} message as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
