Re: Problems with subcolumn retrieval after upgrade from 0.6 to 0.7

2011-04-19 Thread aaron morton
Can you show what comes back from calling Column.getName() Aaron On 20 Apr 2011, at 09:00, aaron morton wrote: > Can you provide a little more info on what I'm seeing here. When name is > shown for the column, are you showing me the entire byte buffer for the name > or just up to limit ? > >

Re: Problems with subcolumn retrieval after upgrade from 0.6 to 0.7

2011-04-19 Thread aaron morton
Can you provide a little more info on what I'm seeing here. When name is shown for the column, are you showing me the entire byte buffer for the name or just up to limit ? Aaron On 20 Apr 2011, at 05:49, Abraham Sanderson wrote: > Ok, set up a unit test for the supercolumns which seem to have

Re: Problems with subcolumn retrieval after upgrade from 0.6 to 0.7

2011-04-19 Thread Abraham Sanderson
Ok, set up a unit test for the supercolumns which seem to have problems, I posted a few examples below. As I mentioned, the retrieved bytes for the name and value appear to have additional data; in previous tests the buffer's position, mark, and limit have been verified, and when I call column.get

Re: Problems with subcolumn retrieval after upgrade from 0.6 to 0.7

2011-04-18 Thread aaron morton
Can you could provide an example of a get_slice request that failed and the columns that were returned, so we can see the actual bytes for the super column and column names. Aaron On 19 Apr 2011, at 09:26, Abraham Sanderson wrote: > I wish it were consistent enough that the answer were simple

Re: Problems with subcolumn retrieval after upgrade from 0.6 to 0.7

2011-04-18 Thread Abraham Sanderson
I wish it were consistent enough that the answer were simple... It varies between just the requested subcolumn to all subcolumns. It always does return the columns in order, and the requested column is always one of the columns returned. However, the slice start is not consistently in the same

Re: Problems with subcolumn retrieval after upgrade from 0.6 to 0.7

2011-04-18 Thread aaron morton
When you run the get_slice which columns are returned ? Aaron On 19 Apr 2011, at 04:12, Abraham Sanderson wrote: > Ok, I made the changes and tried again. Here is the before modifying my > method using a simple get, confirmed the same output in the cli: > > DEBUG [pool-1-thread-2] 2011-04-1

Re: Problems with subcolumn retrieval after upgrade from 0.6 to 0.7

2011-04-18 Thread Abraham Sanderson
Ok, I made the changes and tried again. Here is the before modifying my method using a simple get, confirmed the same output in the cli: DEBUG [pool-1-thread-2] 2011-04-18 09:37:23,910 CassandraServer.java (line 279) get DEBUG [pool-1-thread-2] 2011-04-18 09:37:23,911 StorageProxy.java (line 322)

Re: Problems with subcolumn retrieval after upgrade from 0.6 to 0.7

2011-04-16 Thread aaron morton
Can you run the same request as a get_slice naming the column in the SlicePredicate and see what comes back ? Can you reproduce the fault with logging set at DEBUG and send the logs ? Also, whats the compare function like for your custom type ? Cheers Aaron On 16 Apr 2011, at 07:34, Abraham

Problems with subcolumn retrieval after upgrade from 0.6 to 0.7

2011-04-15 Thread Abraham Sanderson
I'm having some issues with a few of my ColumnFamilies after a cassandra upgrade/import from 0.6.1 to 0.7.4. I followed the instructions to upgrade and everything seem to work OK...until I got into the application and noticed some wierd behavior. I was getting the following stacktrace in cassandr