I've noticed that both 0.5.1 and 0.6b2 return (ReplicationFactor)
identical copies of the data stored in my keyspace whenever I make a
call to get_range_slice or get_range_slices using
ConsistencyLevel.QUORUM.
So with ReplicationFactor set to 2 for my application's KeySpace I get
double the
The apache-cassandra-0.6.0-beta2-bin.tar.gz download contains both these files
in the apache-cassandra-0.6.0-beta2/lib directory:
apache-cassandra-0.6.0-beta1.jar
apache-cassandra-0.6.0-beta2.jar
Given the way the classpath is constructed, it's possible that anyone using
this download is
fwiw, I'm observing what I think is the same issue. I'm using an
unmodified 0.5 release version at this point.
I have a column family that has at most two rows with just one column.
For this CF I seem to be getting back the correct number of keys using
get_range_slice whether I use one or two
for this?
Thanks!
On Mon, Feb 1, 2010 at 4:11 PM, Omer van der Horst Jansen
ome...@yahoo.com wrote:
I checked out the 0.5 branch and ran ant release (on my linux box).
Installed the new tar.gz and ran the test on my Windows laptop as before but
got the same result -- the key isn't deleted from
);
if (key.equals(k.key))
{
System.out.println(but key + k.key
+
should have been removed);
}
}
}
}
Am I using the API correctly in the code above?
-Omer van der Horst Jansen
, 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 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
