You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "C. Scott Andreas (JIRA)" <ji...@apache.org> on 2019/08/02 02:51:00 UTC
[jira] [Updated] (CASSANDRA-14873) Fix missing rows when reading
2.1 SSTables with static columns in 3.0
[ https://issues.apache.org/jira/browse/CASSANDRA-14873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
C. Scott Andreas updated CASSANDRA-14873:
-----------------------------------------
Severity: Critical (was: Normal)
Complexity: Challenging
Discovered By: Fuzz Test
Bug Category: Parent values: Correctness(12982)Level 1 values: Response Corruption / Loss(12987)
Since Version: 3.0.0
> Fix missing rows when reading 2.1 SSTables with static columns in 3.0
> ---------------------------------------------------------------------
>
> Key: CASSANDRA-14873
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14873
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Local Write-Read Paths
> Reporter: Aleksey Yeschenko
> Assignee: Aleksey Yeschenko
> Priority: Urgent
> Fix For: 3.0.18, 3.11.4
>
>
> If a partition has a static row and is large enough to be indexed, then {{firstName}} of the first index block will be set to a static clustering. When deserializing the column index we then incorrectly deserialize the {{firstName}} as a regular, non-{{STATIC}} {{Clustering}} - a singleton array with an empty {{ByteBuffer}} to be exact. Depending on the clustering comparator, this can trip up binary search over {{IndexInfo}} list and cause an incorrect resultset to be returned.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org