ytes 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... It varies
> between just the requested subcolumn to all subcolumns. It always does
> ret
???" Is it
possible that I am inadvertently using a reserved token or something on my
supercolumn name and this is screwing with the slice command?
Abe
On Mon, Apr 18, 2011 at 2:55 PM, aaron morton wrote:
> When you run the get_slice which columns are returned ?
>
>
> Aaron
>
>
, the position shouldn't be changing
at all.
Abe Sanderson
On Sat, Apr 16, 2011 at 5:38 PM, aaron morton wrote:
> 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 D
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
