I inspected some code of the cluster ring.
Thread [ReadStage:6] (Suspended)
SuperColumn.isMarkedForDelete() line: 87
SliceQueryFilter.collectReducedColumns(IColumnContainer,
IteratorIColumn, int) line: 138
Sorry, I'm not following your example.
Could you describe the request you sent, what you expected to get back and what
you actually got back. Are you able to reproduce the fault in a clean install,
e.g. load this data, run these commands and then it goes bang ?
Aaron
On 18 Nov 2010, at
I found the reason (in the view of client side).
I used unit test of my DAO class. the test class inserted test row and
columns before doing test, and then do test, finally delete inserted
columns after test.
The test was succeeded at first. When I do that test again, the test
code attempt to
Hello.
I'm using cassandra (currently 0.7.0-beta3) in JAVA; with library
hector.
It seems that cassandra ignore the count of SliceRange when received
get_slice request.
I traced cassandra source code, and the part of code that retrieving
columns does not get count as parameter. See,
The CassandraServer is not doing the read, step through the code from the call
to readColumnFamily() in getSlice().
The read is passed to the StorageProxy.readProtocol() which looks at the CL and
determines if its a weak or strong read, sends it out to all the replicas and
manages everything.
Just had a quick look at an 0.7b2 install and it appeared to be working as expected.Here's what I got for a row with 50 super columns, that each have 50 columns. I ran the following get_slice calls .get_slice with no super column specified, count=100returned 50 super columns, each with 50
