You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sam Tunnicliffe (JIRA)" <ji...@apache.org> on 2018/09/11 16:06:00 UTC
[jira] [Updated] (CASSANDRA-14716) Protocol frame checksumming
options should not be case sensitive
[ https://issues.apache.org/jira/browse/CASSANDRA-14716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sam Tunnicliffe updated CASSANDRA-14716:
----------------------------------------
Status: Patch Available (was: Open)
Patch + unit test: [here|https://github.com/beobal/cassandra/commit/f9cda7d55cc2b57ba5905f0635275f569d56d4c9]
||utests||dtests||
|[utests|https://circleci.com/gh/beobal/cassandra/437]|[vnodes|https://circleci.com/gh/beobal/cassandra/436] / [no vnodes|https://circleci.com/gh/beobal/cassandra/438]|
> Protocol frame checksumming options should not be case sensitive
> ----------------------------------------------------------------
>
> Key: CASSANDRA-14716
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14716
> Project: Cassandra
> Issue Type: Bug
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Priority: Major
> Fix For: 4.0
>
>
> Protocol v5 adds support for checksumming of native protocol frame bodies. The checksum type is negotiated per-connection via the \{{STARTUP}} message, with two types currently supported, Adler32 and CRC32. The mapping of the startup option value requested by the client to a \{{ChecksumType}} should not be case sensitive, but currently it is.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org