Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0F61E97CA for ; Tue, 16 Dec 2014 13:56:15 +0000 (UTC) Received: (qmail 75667 invoked by uid 500); 16 Dec 2014 13:56:14 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 75635 invoked by uid 500); 16 Dec 2014 13:56:14 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 75623 invoked by uid 99); 16 Dec 2014 13:56:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Dec 2014 13:56:14 +0000 Date: Tue, 16 Dec 2014 13:56:13 +0000 (UTC) From: "Benjamin Lerer (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-6750) Support for UPDATE predicates MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)