Here it is: https://issues.apache.org/jira/browse/CASSANDRA-752
From: Jonathan Ellis jbel...@gmail.com
To: cassandra-user@incubator.apache.org
Sent: Mon, February 1, 2010 5:22:13 PM
Subject: Re: Did CASSANDRA-647 get fixed in 0.5?
Can you create a ticket
I'm running
into an issue with Cassandra 0.5 (the current release version) that
sounds exactly like the description of issue CASSANDRA-647.
I'm
using the Thrift Java API to store a couple of columns in a single row. A few
seconds after that my application deletes the entire row. A plain
647 was committed for 0.5, yes, but CASSANDRA-703 was not. Can you
try the 0.5 branch and see if it is fixed there?
On Mon, Feb 1, 2010 at 3:26 PM, Omer van der Horst Jansen
ome...@yahoo.com wrote:
I'm running
into an issue with Cassandra 0.5 (the current release version) that
sounds exactly
jbel...@gmail.com
To: cassandra-user@incubator.apache.org
Sent: Mon, February 1, 2010 4:52:17 PM
Subject: Re: Did CASSANDRA-647 get fixed in 0.5?
647 was committed for 0.5, yes, but CASSANDRA-703 was not. Can you
try the 0.5 branch and see if it is fixed there?
On Mon, Feb 1, 2010 at 3:26 PM
-- the key isn't deleted from the perspective of
get_range_slice.
Omer
From: Jonathan Ellis jbel...@gmail.com
To: cassandra-user@incubator.apache.org
Sent: Mon, February 1, 2010 4:52:17 PM
Subject: Re: Did CASSANDRA-647 get fixed in 0.5?
647 was committed
