cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dinesh Joshi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-14591) Throw exception if Columns serialized subset encode more columns than possible
Date Tue, 27 Nov 2018 19:04:00 GMT

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

Dinesh Joshi commented on CASSANDRA-14591:
------------------------------------------

LGTM +1. It would be worth adding a unit test to catch a future regression. Either ways I
am fine as this is a small but meaningful fix. Thanks!

> Throw exception if Columns serialized subset encode more columns than possible
> ------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-14591
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14591
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Local Write-Read Paths
>            Reporter: Benedict
>            Assignee: Benedict
>            Priority: Minor
>             Fix For: 4.0, 3.0.x, 3.11.x
>
>
> When deserializing a \{{Columns}} subset via bitset membership, it is trivial to add
a modest probability of detecting corruption, by simply testing that there are no higher bits
set than the candidate \{{Columns}} permits.  This would help mitigate secondary problems
arising from issues like CASSANDRA-14568.



--
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