Tai Khuu Tan commented on CASSANDRA-12659:

The weird thing is only reversed order query return deleted data, even with 
Consistency level set to ALL, normal query won't return deleted data, and there 
are no tombstone also, so I really don't know where the data come from. I tried 
to reproduce it but i couldn't. I will keep trying to see if I can do it.

> 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

Reply via email to