[ 
https://issues.apache.org/jira/browse/CASSANDRA-16319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sam Tunnicliffe updated CASSANDRA-16319:
----------------------------------------
    Resolution: Not A Problem
        Status: Resolved  (was: Open)

Breaking compatibility across different builds of a beta protocol is 
sanctioned/expected, so closing this. ML thread 
[here|https://lists.apache.org/thread.html/rc5f5222219f31f595f75cfa3e9672c0a7069a55c4d93982e384d0054%40%3Cdev.cassandra.apache.org%3E]

> Bump native protocol framing from v5 to v6
> ------------------------------------------
>
>                 Key: CASSANDRA-16319
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16319
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Messaging/Client
>            Reporter: Sam Tunnicliffe
>            Assignee: Sam Tunnicliffe
>            Priority: Normal
>             Fix For: 4.0-beta
>
>
> CASSANDRA-15299 revised the wire format of CQL native protocol to add a 
> framing layer around the existing CQL messages. This was originally targetted 
> at protocol v5, which is (still) currently in beta. There's a complication 
> with this though; while v5-beta is supported in Cassandra 3.11.x and 4.0.0, 
> the new wire format is only committed to trunk (4.0.0). This means that if 
> clients upgrade to a version of their driver which supports the new wire 
> format (3.10.0 for the java driver, python driver is not yet offically 
> released), connections to Cassandra 3.11.x nodes will break if the client 
> specifies v5-beta as the preferred protocol version. 
> Without the wire format changes the v5 changelog is pretty minimal, but 
> pulling v5 support from 3.11.x would make for a pretty bad user experience, 
> despite it being "only" a beta.
> I propose finalizing CASSANDRA-14973 to promote v5 from beta to a final 
> version and bumping the new wire format changes to v6-beta, making both of 
> these changes in 4.0 and 3.11. Because v5 requires the beta flag to be set in 
> the frame header if using a beta version, this requires that users upgrade 
> clusters to a version with v5-final before upgrading to a driver with 
> v5-final. We should include this in NEWS.txt
> The changes required to Cassandra itself are minor, as are the corresponding 
> patches to the java and python drivers.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to