Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 283ED200B82 for ; Fri, 16 Sep 2016 21:24:23 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 26F2B160AC4; Fri, 16 Sep 2016 19:24:23 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 92F53160AB7 for ; Fri, 16 Sep 2016 21:24:22 +0200 (CEST) Received: (qmail 35270 invoked by uid 500); 16 Sep 2016 19:24:21 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 35243 invoked by uid 99); 16 Sep 2016 19:24:21 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Sep 2016 19:24:21 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 907AC2C014C for ; Fri, 16 Sep 2016 19:24:21 +0000 (UTC) Date: Fri, 16 Sep 2016 19:24:21 +0000 (UTC) From: "Tai Khuu Tan (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CASSANDRA-12659) Query in reversed order brough back deleted data MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 16 Sep 2016 19:24:23 -0000 Tai Khuu Tan created CASSANDRA-12659: ---------------------------------------- Summary: 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)