You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2014/08/28 08:23:58 UTC
[jira] [Commented] (CASSANDRA-7804) Confusing error message when
condition is set on primary key column
[ https://issues.apache.org/jira/browse/CASSANDRA-7804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14113414#comment-14113414 ]
Sylvain Lebresne commented on CASSANDRA-7804:
---------------------------------------------
+1, but I'll note that I would have no problem fixing this in 2.0 too.
> Confusing error message when condition is set on primary key column
> -------------------------------------------------------------------
>
> Key: CASSANDRA-7804
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7804
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Tyler Hobbs
> Assignee: Tyler Hobbs
> Priority: Minor
> Fix For: 2.1.1
>
> Attachments: 7804-2.1.txt
>
>
> If you set a CAS condition on a primary key column, you'll get an error that's somewhat confusing:
> {noformat}
> cqlsh:ks1> CREATE TABLE mytable (a int PRIMARY KEY, b int);
> cqlsh:ks1> UPDATE mytable SET b = 0 WHERE a = 0 IF a = 0;
> code=2200 [Invalid query] message="PRIMARY KEY part a found in SET part"
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)