[CASSANDRA-12659] Query in reversed order brough back deleted data

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Duplicate
• Component/s: Legacy/Core

Environment

Cassandra 3.0.5, 6 nodes cluster

• Severity: Normal
• Since Version: 3.0.5
• Assignee: Unassigned
• Reporter: Tai Khuu Tan
• Created: 16/Sep/16 19:23
• Updated: 16/Apr/19 09:30
• Resolved: 22/Sep/16 23:41

Description

We have and issues with our Cassandra 3.0.5. After we deleted a large amount of data in the multiple partition keys. Query those partition keys with reversed order on a clustering key return the deleted data. I have checked and there are no tombstones left. All of them are deleted. So I don't know where or how can those deleted data still exist. Is there any other place that Cassandra will read data when query in reverse order compare to normal order ?
the schema is very simple

CREATE TABLE table ( uid varchar, version timestamp, data1 varchar, data2 varchar, data3 varchar, data4 varchar, data5 varchar, PRIMARY KEY (uid, version, data1 , data2 , data3 , data4 ) ) with compact storage;

Query are doing reverse order on column timestamp

Ex:

select * from data where uid="uid1" order by version DESC

Issue Links

• duplicates: CASSANDRA-11733 SSTableReversedIterator ignores range tombstones