cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-12142) Add "beta" version native protocol flag
Date Wed, 06 Jul 2016 16:10:11 GMT


Tyler Hobbs commented on CASSANDRA-12142:

[~ifesdjeen] sure, feel free to take this.

bq. As for the flag itself, we probably should add it to each message "flags" byte (2nd byte
of the header) since the protocol version is more associated to messages than connection in

My thought was that we could avoid wasting the flag bit and simply validate beta version connections
at startup.  However, I do agree that the message header flags are a more natural location,
so if you're not concerned about using a flag bit for that, I'm +1.

> Add "beta" version native protocol flag
> ---------------------------------------
>                 Key: CASSANDRA-12142
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: CQL
>            Reporter: Tyler Hobbs
>              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