Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 7 Dec 2011 16:10:41 +0000 (UTC)
From: "Sylvain Lebresne (Resolved) (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <52997068.49646.1323274241577.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1789766085.37022.1319906852462.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (CASSANDRA-3422) Can create a Column Family with
 comparator CounterColumnType which is subsequently unusable
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sylvain Lebresne resolved CASSANDRA-3422.
-----------------------------------------

       Resolution: Fixed
    Fix Version/s: 0.8.9
    
> Can create a Column Family with comparator CounterColumnType which is subsequently unusable
> -------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-3422
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3422
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.8.0
>            Reporter: Kelley Reynolds
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>             Fix For: 0.8.9, 1.0.6
>
>         Attachments: 3422-v2.patch, 3422.patch
>
>
> It's probably the case that this shouldn't be allowed at all but one is currently allowed to create a Column Family with comparator CounterColumnType which then appears unusable.
> CREATE COLUMNFAMILY comparator_cf_counter (id text PRIMARY KEY) WITH comparator=CounterColumnType
> # Fails
> UPDATE comparator_cf_counter SET 1=1 + 1 WHERE id='test_key'
> Error => invalid operation for non commutative columnfamily comparator_cf_counter

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira