You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jason Kania (JIRA)" <ji...@apache.org> on 2014/12/15 04:38:13 UTC

[jira] [Commented] (CASSANDRA-6173) Unable to delete multiple entries using In clause on clustering part of compound key

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

Jason Kania commented on CASSANDRA-6173:
----------------------------------------

Inconsistencies like these, especially when undocumented, are obnoxious because they waste a person's time to figure out. At least document it in the meantime. In general the delete documentation could use more detail as its fairly weak.

> Unable to delete multiple entries using In clause on clustering part of compound key
> ------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-6173
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6173
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Ashot Golovenko
>            Priority: Minor
>
> I have the following table:
> CREATE TABLE user_relation (
>     u1 bigint,
>     u2 bigint,
>     mf int,
>     i boolean,
>     PRIMARY KEY (u1, u2));
> And I'm trying to delete two entries using In clause on clustering part of compound key and I fail to do so:
> cqlsh:bm> DELETE from user_relation WHERE u1 = 755349113 and u2 in (100003404014120, 100002537242743);
> Bad Request: Invalid operator IN for PRIMARY KEY part u2
> Although the select statement works just fine:
> cqlsh:bm> select * from user_relation WHERE u1 = 755349113 and u2 in (100003404014120, 100002537242743);
>  u1        | u2              | i    | mf
> -----------+-----------------+------+----
>  755349113 | 100002537242743 | null | 27
>  755349113 | 100003404014120 | null |  0
> (2 rows)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)