Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 3 Jun 2011 05:42:47 +0000 (UTC)
From: "Stu Hood (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <1827308160.65097.1307079767321.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2118571153.11559.1305322488305.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CASSANDRA-2650) AntiEntropyServiceCounterTest
 writes CounterUpdateColumn to disk
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-2650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13043219#comment-13043219 ] 

Stu Hood commented on CASSANDRA-2650:
-------------------------------------

Just noticed this issue is still open, which is helpful, because I found a new instance of the problem: {{db.RecoveryManagerTest.testRecoverCounter}} is writing a CounterColumn without using CounterMutation.

> AntiEntropyServiceCounterTest writes CounterUpdateColumn to disk
> ----------------------------------------------------------------
>
>                 Key: CASSANDRA-2650
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2650
>             Project: Cassandra
>          Issue Type: Test
>          Components: Tests
>            Reporter: Stu Hood
>            Assignee: Stu Hood
>            Priority: Minor
>              Labels: counters
>             Fix For: 1.0
>
>         Attachments: 0001-Make-IMutation-more-uniform-and-apply-IMutation-in-Uti.txt
>
>
> By using an unwrapped RowMutation to apply a counter update, AESCT was applying/flushing a CounterUpdateColumn to disk. I'm still not a fan of the magic that is going on with CUC, but for now fixing misuses is the most reasonable approach.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira