[
https://issues.apache.org/jira/browse/CASSANDRA-6750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14248263#comment-14248263
]
Benjamin Lerer commented on CASSANDRA-6750:
-------------------------------------------
I think that part of the problem here is the fact that for years people have
worked with SQL where this operation is perfectly normal (I do not know any
serious relational database that do not support that). I know that we have
other problem that relational database do not have but from a user point of
view it is not obvious and it is really confusing.
What is the problem of read before write?
> 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)
