You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jens Rantil (JIRA)" <ji...@apache.org> on 2014/12/01 13:11:12 UTC

[jira] [Updated] (CASSANDRA-8397) Support UPDATE with IN requirement for clustering key

     [ https://issues.apache.org/jira/browse/CASSANDRA-8397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jens Rantil updated CASSANDRA-8397:
-----------------------------------
    Summary: Support UPDATE with IN requirement for clustering key  (was: Support UPDATE with IN for clustering key)

> 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
>            Priority: Minor
>
> {noformat}
> CREATE TABLE tink.events (
>     userid uuid,
>     id timeuuid,
>     content text,
>     type text,
>     PRIMARY KEY (userid, id)
> )
> # Add data
> cqlsh:tink> 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)