cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6750) Support for UPDATE predicates
Date Tue, 16 Dec 2014 17:05:13 GMT

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

Aleksey Yeschenko commented on CASSANDRA-6750:
----------------------------------------------

In this case it's not just a regular read before write (which we used to do until 1.2? for
index updates, out of necessity, which we still do for counters (locally) and for lists (a
design mistake)). This would require a 2i read before write, potentially a very expensive
one, and unpredictable in general. Such writes would also not be retriable in an idempotent
fashion, which is a big no-no when it comes to C* writes.

> Support for UPDATE predicates
> -----------------------------
>
>                 Key: CASSANDRA-6750
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6750
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API, Core
>         Environment: 2.0.3
>            Reporter: nivance
>            Assignee: Benjamin Lerer
>            Priority: Minor
>              Labels: cql3, ponies
>
> cqlsh:spdatarp> UPDATE t_spdatarpro_ro SET amount = 10  WHERE messageid = '123456';
> Bad Request: Non PRIMARY KEY messageid found in where clause
> In this case, messageid is the secend index. I want to update all rows which messageid
is '123456', but it failed



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

Mime
View raw message