Hi,
this is true for CQL2, it doesn't work for CQL3:
cqlsh:c4> SELECT id from some_table WHERE indexed_column='test';
...
cqlsh:c4> SELECT KEY from some_table WHERE indexed_column='test';
Bad Request: Undefined name key in selection clause
Perhaps you meant to use CQL 2? Try using the -2 option w
> What are we doing wrong? Can it be that Cassandra is actually trying to read
> all the CF data rather than just the keys! (actually, it doesn't need to go
> to the users CF at all - all the data it needs is in the index CF)
>
Data is not stored as a BTree, that's the RDBMS approach. We hit th
IMHO: user_name is not a column, it is the row key. Therefore, according to
http://thelastpickle.com/2011/07/04/Cassandra-Query-Plans/ , the row does not
contain a relevant column index, which causes the iterator to read each column
(including value) of each row.
I believe that instead of refer
Hi,
if you are able to reproduce the issue, file a ticket on
https://issues.apache.org/jira/browse/CASSANDRA - my experience is
developers respond quickly on issues that are clearly a bug.
regards,
ondrej cernos
On Thu, Apr 25, 2013 at 10:03 AM, Tamar Rosen wrote:
> Hi,
>
> We have a case of
