Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of jbellis@gmail.com designates
 74.125.82.171 as permitted sender)
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;
        b=jxAITCjMutBFFhoCj1pOJLUA4CGTU9R12Y2HJjD0tyJG9+JqEbZZQG3RCoVra9y/Z4
         iwBrpzmOR8IegnRtrTDorl9Hno1IIS0D0rWlFczkbrgPw1o4b5gxCvSgT7ZzHbbrzL7t
         xMZM+PhEqgeLzWZWn9HVihAcHeezx35whT7sc=
MIME-Version: 1.0
In-Reply-To: <4BFE7355.3040800@dehora.net>
References: <4BFE7355.3040800@dehora.net>
From: Jonathan Ellis <jbellis@gmail.com>
Date: Thu, 27 May 2010 07:57:13 -0600
Message-ID: <AANLkTikJkY_uD3ZgqiFKJF086hzYDYCKWPYsQFbEgGCO@mail.gmail.com>
Subject: Re: Remove and BytesType
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1

remove to a full row doesn't touch comparewith at all.  I think that's
a red herring.  More likely data in that row was created with a
higher-res timestamp than the delete was issued at.

On Thu, May 27, 2010 at 7:27 AM, Bill de hOra <bill@dehora.net> wrote:
> Saw some behaviour today on Cassandra 0.6.1 -
>
> After running a remove command on a row in a CF whose CompareWith was
> BytesType the row was still there, and still there after bouncing the
> server. This was the case for hector/cli. When I changed the CompareWith to
> UTF8Type, new rows added could be removed (old rows wouldn't delete).
>
> Was wondering if anyone else had seen this.
>
> Bill
>
>


-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of Riptano, the source for professional Cassandra support
http://riptano.com