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

Sam Tunnicliffe updated CASSANDRA-16374:
----------------------------------------
          Fix Version/s:     (was: 4.0-beta)
                         4.0
                         4.0-beta5
          Since Version: 4.0-beta4
    Source Control Link: 
https://github.com/apache/cassandra/commit/a0441eb66b1976865c105069e9964104720db7fb
             Resolution: Fixed
                 Status: Resolved  (was: Ready to Commit)

Committed, thanks.

> Restore check for consistent native protocol versions for connection
> --------------------------------------------------------------------
>
>                 Key: CASSANDRA-16374
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16374
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Messaging/Client
>            Reporter: Sam Tunnicliffe
>            Assignee: Sam Tunnicliffe
>            Priority: Normal
>              Labels: protocolv5
>             Fix For: 4.0-beta5, 4.0
>
>
> In protocol v4 and earlier, the frame header is checked during 
> deserialization to ensure that the version matches the one negotiated for the 
> connection.
> The original intention was to remove this version id from the frame (renamed 
> to envelope in v5) header. However, there is value in keeping this check as 
> well as the the one for the beta flag, so it remains in the frame/envelope 
> format. The validation itself however, was removed by some refactoring as 
> part of CASSANDRA-15299 and should be added back for all protocol versions 
> before finalizing v5 and cutting a release candidate. The text detailing its 
> removal also remains in the proposed spec update attached to CASSANDRA-14688, 
> which also needs to be updated.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to