Remove and BytesType

[Bill de hOra <bi...@dehora.net>]

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

Re: Remove and BytesType

[Bill de hOra <bi...@dehora.net>]

 > More likely data in that row was created with a
 > higher-res timestamp than the delete was issued at.

Indeed - the problem was nanos v millis with a bit of clock skew thrown 
in :)

Bill

Jonathan Ellis wrote:
> 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 <bi...@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
>>
>>
> 
> 
> 

Re: Remove and BytesType

[Jonathan Ellis <jb...@gmail.com>]

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 <bi...@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

Re: Remove and BytesType

[Philip Stanhope <ps...@wimba.com>]

Could you clarify what you mean by "remove command"? Remove all columns leaving a row key?

Did you use nodetool to force a flush and then compact after GCGraceSeconds?

On May 27, 2010, at 9:27 AM, Bill de hOra 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
>