That feels like a serious bug. Definitely file a JIRA with as many details as possible. https://issues.apache.org/jira/browse/CASSANDRA/
On Tue, Mar 1, 2016 at 4:38 PM Rakesh Kumar <dcrunch...@aim.com> wrote: > Looks like Bloom filter size was the issue. Once I disabled it, the query > returns rows correctly, but it was terrible slow (expected since it will > hit SStable every time). > > > -----Original Message----- > From: Rakesh Kumar <dcrunch...@aim.com> > To: user <user@cassandra.apache.org> > Sent: Tue, Mar 1, 2016 4:57 pm > Subject: Re: Querying on index > > > At this time no one else is using this table. So the data is static. > > -----Original Message----- > From: Rakesh Kumar > To: user > Sent: Tue, Mar 1, 2016 4:54 pm > Subject: Querying on index > > Cassandra: 3.3On my test system I create a tablecreate table eventinput( > event_id varchar , event_class_cd int , event_ts timestamp , client_id > varchar , event_message text , primary key ((client_id,event_id),event_ts)) > I created an index on client_id create index idx1 on > eventinput(client_id);When I query select *from eventinputwhere client_id = > 'aa' ALLOW filtering ;I get random results. One time it is 200, another > time 400 or 500 or 600 and sometimes 0.Why ? >
