[
https://issues.apache.org/jira/browse/CASSANDRA-6750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14248078#comment-14248078
]
Sylvain Lebresne commented on CASSANDRA-6750:
---------------------------------------------
I'm not entirely sure we should support this at all because that would require
a read-before-write and I'd prefer leaving that kind of thing explicit to the
user (by issuing a select, and then an update). And before someone bring this
up, I'm well aware that we already have a read-before-write for lists, but
that's more an example of a mistake we made and shouldn't reproduce than
anything else.
> 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)
