cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-12142) Add "beta" version native protocol flag
Date Tue, 19 Jul 2016 13:39:20 GMT


Sylvain Lebresne commented on CASSANDRA-12142:

bq. should we make it configurable in {{cassandra.yaml}}?

Less config options are better, so I'd say we wait until someone comes up with a genuine need
for it before bothering.

bq. just in case driver implementor would decide to set this flag to true by default, it might
be a problem.

There might be many problem if you assume stupid driver implementors, and that's the least
of them, so let's not assume it.

> Add "beta" version native protocol flag
> ---------------------------------------
>                 Key: CASSANDRA-12142
>                 URL:
>             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

View raw message