Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 22 Oct 2013 20:42:51 +0000 (UTC)
From: "Constance Eustace (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12674709.1382299416390.106234.1382474571595@arcas>
In-Reply-To: <JIRA.12674709.1382299416390@arcas>
References: <JIRA.12674709.1382299416390@arcas>
Subject: [jira] [Comment Edited] (CASSANDRA-6220) Unable to select multiple
 entries using In clause on clustering part of compound key
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13802237#comment-13802237 ] 

Constance Eustace edited comment on CASSANDRA-6220 at 10/22/13 8:41 PM:
------------------------------------------------------------------------

If I do this sequence:

DROP SCHEMA
CREATE SCHEMA
CREATE INITIAL DATA (i.e. no updates to existing data)
NODETOOL COMPACT <-- magic sauce
MASSIVE INSERT + SIMULTANEOUS UPDATES to INITIAL DATA

does not reproduce. The nodetool compact after the schema creation seems to reset/stabilize the database. I used to replicate very reliably after about 300,000 inserts / 2000 updates. Now I do 1.75million inserts with 20,000 updates and no reproduction.

Obviously you could probably run the nodetool compact after the SCHEMA creation, and then do initial data creation/update+insert run


was (Author: cowardlydragon):
If I do this sequence:

DROP SCHEMA
CREATE SCHEMA
CREATE INITIAL DATA (i.e. no updates to existing data)
NODETOOL COMPACT <-- magic sauce
MASSIVE INSERT + SIMULTANEOUS UPDATES to INITIAL DATA

does not reproduce. The nodetool compact after the schema creation seems to reset/stabilize the database. I used to replicate very reliably after about 300,000 inserts / 2000 updates. Now I do 1.75million inserts with 20,000 updates and no reproduction.


> 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)