Re: Secondary Index on table with a lot of data crashes Cassandra

2013-05-02 Thread Ondřej Černoš
> Select KEY from users where status = 2; > > ** ** > > Always glad to share a theory with a friend…. > > ** ** > > ** ** > > *From:* Tamar Rosen [mailto:ta...@correlor.com] > *Sent:* Thursday, April 25, 2013 11:04 AM > *To:* user@cassandra.apa

Re: Secondary Index on table with a lot of data crashes Cassandra

2013-04-28 Thread aaron morton
me as if it were a column, you > need to refer to it via the reserved word “KEY”, e.g.: > > Select KEY from users where status = 2; > > Always glad to share a theory with a friend…. > > > From: Tamar Rosen [mailto:ta...@correlor.com] > Sent: Thursday, April 25, 2013 11

RE: Secondary Index on table with a lot of data crashes Cassandra

2013-04-25 Thread moshe.kranc
M To: user@cassandra.apache.org Subject: Secondary Index on table with a lot of data crashes Cassandra Hi, We have a case of a reproducible crash, probably due to out of memory, but I don't understand why. The installation is currently single node. We have a column family with approx 5 rows.

Re: Secondary Index on table with a lot of data crashes Cassandra

2013-04-25 Thread Ondřej Černoš
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

Secondary Index on table with a lot of data crashes Cassandra

2013-04-25 Thread Tamar Rosen
Hi, We have a case of a reproducible crash, probably due to out of memory, but I don't understand why. The installation is currently single node. We have a column family with approx 5 rows. In cql, the CF definition is: CREATE TABLE users ( user_name text PRIMARY KEY, big_json text,