[
https://issues.apache.org/jira/browse/CASSANDRA-12142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394581#comment-15394581
]
Alex Petrov commented on CASSANDRA-12142:
-----------------------------------------
Yes, sorry, overlooked it somehow. Fixing it was
[trivial|https://github.com/ifesdjeen/cassandra/commit/dd0bd90bc11cabe9dfa103bf42563e7f310192a1#diff-13d5c04f62552ff47ad78a3ad932ca5eR38]:
we should use v6 for "unsupported" protocol version. v5 is supported and
throws "use beta flag" type of error message.
I've rebased and re-triggered CI just in case. Also, I've moved doc changes to
v5 document.
> 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)
