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

Wei Deng commented on CASSANDRA-12659:
--------------------------------------

Did you preserve the SSTables (snapshot) when you were able to reproduce the 
problem? If yes, it will be useful to use "nodetool getendpoints" and "nodetool 
getsstables" to extract a number of SSTables that contains the partition in 
question and upload them here along with the schema (assuming it doesn't 
contain sensitive information). If you're no longer able to reproduce the 
problem, then there is no need to provide the SSTables.

Without a repro case, it will be hard for people to look into it. However, 
filing this JIRA right now is still valuable because if other people run into 
the same problem in a different occasion, they will have something to compare 
notes to determine if this is a real problem. If after a while nobody else runs 
into this issue and you are still not able to reproduce it, the JIRA could end 
up getting closed eventually.

> Query in reversed order brough back deleted data
> ------------------------------------------------
>
>                 Key: CASSANDRA-12659
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12659
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: Cassandra 3.0.5, 6 nodes cluster
>            Reporter: Tai Khuu Tan
>
> 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
> {noformat}
> 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;
> {noformat}
> Query are doing reverse order on column timestamp
> Ex:
> {noformat}
> select * from data where uid="uid1" order by version DESC
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to