From cassandra-user-return-1169-apmail-incubator-cassandra-user-archive=incubator.apache.org@incubator.apache.org Mon Nov 09 05:11:06 2009 Return-Path: Delivered-To: apmail-incubator-cassandra-user-archive@minotaur.apache.org Received: (qmail 23984 invoked from network); 9 Nov 2009 05:11:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 9 Nov 2009 05:11:06 -0000 Received: (qmail 19578 invoked by uid 500); 9 Nov 2009 05:11:06 -0000 Delivered-To: apmail-incubator-cassandra-user-archive@incubator.apache.org Received: (qmail 19521 invoked by uid 500); 9 Nov 2009 05:11:06 -0000 Mailing-List: contact cassandra-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cassandra-user@incubator.apache.org Delivered-To: mailing list cassandra-user@incubator.apache.org Received: (qmail 19512 invoked by uid 99); 9 Nov 2009 05:11:06 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Nov 2009 05:11:06 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jbellis@gmail.com designates 209.85.219.209 as permitted sender) Received: from [209.85.219.209] (HELO mail-ew0-f209.google.com) (209.85.219.209) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Nov 2009 05:10:58 +0000 Received: by mail-ew0-f209.google.com with SMTP id 5so2630468ewy.12 for ; Sun, 08 Nov 2009 21:10:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:content-type :content-transfer-encoding; bh=aO86hzaWRKpEoiL13rqwcc0ytayw+fi7aKmuUWxMS0U=; b=wD7Ggtaz1af1nMAjVdvDp+7VkNw8Ubnx7e5JlFTAVsmsIOtCHTxovEXkhhFHfP6bZd jQMvax0E34oEk+jIRzOKCNStJXNjPA8aLoOhehxOBy2AdIx0X6KAlhPLJEtWjaz+TCL2 7FXYTz7uva4zh4vmFeuZ3UGtH6kA9KAiL8Fvs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=BcVVQNb8AbvrTP4m+IoUkHzT/mWtoYB8BSyh/IzhLI2DmvhqxaKpRuMcUw+Y8boStL OMxYStsHcZYhJmR8AgztkQ1TQzKaS/EWPqEQCRaP/72Qy6qfkubjJNsaOFFzlxqrSjPi AIQQf/qV0/bTsK0cGQx/hfLTeL9r4uV8+GBgE= MIME-Version: 1.0 Received: by 10.216.93.77 with SMTP id k55mr2401370wef.196.1257743438131; Sun, 08 Nov 2009 21:10:38 -0800 (PST) In-Reply-To: References: From: Jonathan Ellis Date: Sun, 8 Nov 2009 23:10:18 -0600 Message-ID: Subject: Re: why does remove need a timestamp? To: cassandra-user@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org it's to say when the remove occurred, not to match the timestamp you insert= ed On Sun, Nov 8, 2009 at 10:57 PM, Ramzi Rabah wrote: > Hello all: > I am confused about the need of passing a =A0timestamp for the remove > operation. Why does the remove operation in Cassandra require a > timestamp? What happens if I provide a remove call with a different > timestamp than what I inserted, will the row still be deleted? > > Thanks > Ray >