[
https://issues.apache.org/jira/browse/CASSANDRA-12142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15384123#comment-15384123
]
Alex Petrov commented on CASSANDRA-12142:
-----------------------------------------
Do we want this feature to be enabled by default, or should we make it
configurable in {{cassandra.yaml}}? Something like
{{allow_native_protocol_beta_connections}} setting that's false by default?
Although I've made a patch to client so that it'd connect by default using
{{v4}}, and only {{v5}} is only able if it's passed explicitly with {{useBeta}}
flag set to true. Although just in case driver implementor would decide to set
this flag to true by default, it might be a 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)
