[
https://issues.apache.org/jira/browse/CASSANDRA-7235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14036090#comment-14036090
]
Jonathan Ellis commented on CASSANDRA-7235:
-------------------------------------------
[~krummas] to review
> ColumnStats min/max column names does not account for range thombstones,
> making deleted data resurrect at random
> ----------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-7235
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7235
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Oleg Anastasyev
> Attachments: ColumnStatsOfRangeThombstones.txt
>
>
> This issue can be reproduced in cqlsh:
> {code}
> create table test1( a int, b int, primary key(a,b));
> INSERT INTO test1(a,b) values (1,1);
> INSERT INTO test1(a,b) values (1,2);
> INSERT INTO test1(a,b) values (1,3);
> INSERT INTO test1(a,b) values (1,4);
> INSERT INTO test1(a,b) values (1,5);
> INSERT INTO test1(a,b) values (1,6);
> -- flush memtable here
> delete from test1 where a=1 and b=6;
> INSERT INTO test1(a,b) values (2,2);
> -- flush memtable here
> select * from test1 where a=1 and b=6;
> a | b
> ---+---
> 1 | 6
> {code}
> Voila!
> The problem is in columnStats accounting for min and max columns names. range
> tombstones are not accounted there, so sstables get omitted on slice query
> read, if they have only range thombsones in some range.
> Also while debugged this found a problem in LazilyCompactedRow:
> RangeThombstones processing of timestamps histogram were implemented wrong in
> CASSANDRA-6522 - no range thobmstones are actuallu accessible in
> deletionInfo().rangeIterator(), so fixed it as well.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
