cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jens Rantil (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8397) Support UPDATE with IN requirement for clustering key
Date Tue, 09 Dec 2014 09:54:12 GMT

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

Jens Rantil commented on CASSANDRA-8397:
----------------------------------------

> My plan is to reuse the restriction code of SelectStatement for update and delete statements.
If it works well it would make it easy to support for delete and update all the possible restriction
cases that are currently supported by the select.

Just curious, performancewise, would a multi-update require a single commitlog item or multiple
commitlog items?

> 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