cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Tunnicliffe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-14716) Protocol frame checksumming options should not be case sensitive
Date Tue, 27 Nov 2018 12:52:00 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-14716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16700372#comment-16700372
] 

Sam Tunnicliffe commented on CASSANDRA-14716:
---------------------------------------------

Rebased and updated branch to uppercase the enum value.
||branch||CI||
|[14716-trunk|https://github.com/beobal/cassandra/tree/14716-trunk]|[circle|https://circleci.com/gh/beobal/workflows/cassandra/tree/cci%2F14716-trunk]|


> 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
>          Components: CQL
>            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


Mime
View raw message