[ https://issues.apache.org/jira/browse/CASSANDRA-10618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ZhaoYang updated CASSANDRA-10618: --------------------------------- Environment: Cassandra 2.1.2 (was: Windows 7, Cassandra 2.1.2) > Read ghost data > --------------- > > Key: CASSANDRA-10618 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10618 > Project: Cassandra > Issue Type: Bug > Environment: Cassandra 2.1.2 > Reporter: ZhaoYang > > In a table( pk, ck, value) with 1 partition key and 1 clustering key. > SELECT * FROM table where pk='PK1' AND ck1='CK1' (full primary keys) -> will > return a row that doesn't appear in range scan query (SELECT * FROM table > where pk='PK1'). > I tested it with Java Driver 2.1.5 as well as DevCenter. Our environment has > only 1 node and replication factor 1. It's our development DB, multiple > developers are accessing it. And we are using client-side timestamp generator. > If I use nodetool to compact this table, this ghost data will disappear. > What can be the cause? because of un-order timestamp? > Thank you very much. -- This message was sent by Atlassian JIRA (v6.3.4#6332)