cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Lerer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8397) Support UPDATE with IN requirement for clustering key
Date Mon, 23 Mar 2015 10:44:11 GMT

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

Benjamin Lerer commented on CASSANDRA-8397:
-------------------------------------------

[~ztyx] For an {{IN}} on a clustering key the code will create only one {{Mutation}} so the
commit log will insert only one item.

> Support UPDATE with IN requirement for clustering key
> -----------------------------------------------------
>
>                 Key: CASSANDRA-8397
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8397
>             Project: Cassandra
>          Issue Type: Wish
>            Reporter: Jens Rantil
>            Assignee: Benjamin Lerer
>            Priority: Minor
>
> {noformat}
> CREATE TABLE events (
>     userid uuid,
>     id timeuuid,
>     content text,
>     type text,
>     PRIMARY KEY (userid, id)
> )
> # Add data
> cqlsh:mykeyspace> UPDATE events SET content='Hello' WHERE userid=57b47f85-56c4-4968-83cf-4c4e533944e9
AND id IN (046e9da0-7945-11e4-a76f-770773bbbf7e, 046e0160-7945-11e4-a76f-770773bbbf7e);
> code=2200 [Invalid query] message="Invalid operator IN for PRIMARY KEY part id"
> {noformat}
> I was surprised this doesn't work.



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

Mime
View raw message