>
> cqlsh:Sessions> select * from "Items" where "mahoutItemid" =
> 610866442877251584;
>
> key| mahoutItemid
> +
> 687474703a2f2f6573706f7| 610866442877251584
>
> unsupported operand type(s) for /: 'NoneType' and 'float'
Can you
Thanks!
The creation of the new CF worked pretty well and fast! Unfortunately, I was
unable to trace the request made using secondary indexes:
cqlsh:Sessions> select * from "Items" where key = '687474703a2f2f6573706f7';
key| mahoutItemid
+---
Try the request tracing in 1.2
http://www.datastax.com/dev/blog/tracing-in-cassandra-1-2 it may point to the
different.
> In our model the secondary index in also unique, as the primary key is. Is it
> better, in this case, to create another CF mapping the secondary index to the
> key?
IMHO i
Hi all!
We are using Cassandra 1.2.1 with a 8 node cluster running at Amazon. We
started with 6 nodes and added the 2 later. When performing some reads in
Cassandra, we observed a high difference between gets using the primary key and
gets using secondary indexes:
[default@Sessions] get Users
