[ https://issues.apache.org/jira/browse/CASSANDRA-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13802269#comment-13802269 ]
Constance Eustace edited comment on CASSANDRA-6220 at 10/22/13 9:11 PM: ------------------------------------------------------------------------ I was able to reproduce the original way of reproduction (drop schema, create schema, INSERT / UPDATE with no nodetool compact in there). Post-repair of the corruption seemed to require nodetool compact, invalidatekeycache, and/or possibly flush. Now that I've repaired. I'm going to run a 3.5 million insert + simulataneous update run to see if the nodetool compact repair makes the data more durable. was (Author: cowardlydragon): It may also require invalidatekeycache / caches, possibly with a flush in there as well... > Unable to select multiple entries using In clause on clustering part of > compound key > ------------------------------------------------------------------------------------ > > Key: CASSANDRA-6220 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6220 > Project: Cassandra > Issue Type: Bug > Components: Core > Reporter: Ashot Golovenko > Attachments: inserts.zip > > > I have the following table: > CREATE TABLE rating ( > id bigint, > mid int, > hid int, > r double, > PRIMARY KEY ((id, mid), hid)); > And I get really really strange result sets on the following queries: > cqlsh:bm> SELECT hid, r FROM rating WHERE id = 755349113 and mid = 201310 > and hid = 201329320; > hid | r > -----------+-------- > 201329320 | 45.476 > (1 rows) > cqlsh:bm> SELECT hid, r FROM rating WHERE id = 755349113 and mid = 201310 > and hid = 201329220; > hid | r > -----------+------- > 201329220 | 53.62 > (1 rows) > cqlsh:bm> SELECT hid, r FROM rating WHERE id = 755349113 and mid = 201310 > and hid in (201329320, 201329220); > hid | r > -----------+-------- > 201329320 | 45.476 > (1 rows) <-- WRONG - should be two records > As you can see although both records exist I'm not able the fetch all of them > using in clause. By now I have to cycle my requests which are about 30 and I > find it highly inefficient given that I query physically the same row. > More of that - it doesn't happen all the time! For different id values > sometimes I get the correct dataset. > Ideally I'd like the following select to work: > SELECT hid, r FROM rating WHERE id = 755349113 and mid in ? and hid in ?; > Which doesn't work either. -- This message was sent by Atlassian JIRA (v6.1#6144)