Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6AE986908 for ; Mon, 13 Jun 2011 12:59:37 +0000 (UTC) Received: (qmail 79363 invoked by uid 500); 13 Jun 2011 12:59:35 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 79344 invoked by uid 500); 13 Jun 2011 12:59:35 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 79336 invoked by uid 99); 13 Jun 2011 12:59:35 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Jun 2011 12:59:35 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [204.13.248.66] (HELO mho-01-ewr.mailhop.org) (204.13.248.66) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Jun 2011 12:59:27 +0000 Received: from 75-166-66-241.hlrn.qwest.net ([75.166.66.241] helo=[192.168.0.2]) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.72) (envelope-from ) id 1QW6jS-000B7v-Fk for user@cassandra.apache.org; Mon, 13 Jun 2011 12:59:06 +0000 X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 75.166.66.241 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1/55+VY3d03TmgwKl6d47yUPOgJ+hTkF5k= Message-ID: <4DF60996.3050506@dude.podzone.net> Date: Mon, 13 Jun 2011 06:59:02 -0600 From: AJ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: user@cassandra.apache.org Subject: Docs: "Why do deleted keys show up during range scans?" Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit http://wiki.apache.org/cassandra/FAQ#range_ghosts "So to special case leaving out result entries for deletions, we would have to check the entire rest of the row to make sure there is no undeleted data anywhere else either (in which case leaving the key out would be an error)." The above doesn't read well and I don't get it. Can anyone rephrase it or elaborate? Thanks!