cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-2650) Tests write CounterUpdateColumns to disk
Date Thu, 10 Nov 2011 14:23:51 GMT

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

Sylvain Lebresne resolved CASSANDRA-2650.
-----------------------------------------

    Resolution: Fixed

Time to close this one.
I don't see the RecoveryManagerTest.testRecoverCounter instance a a real problem since it
doesn't write a CounterUpdateColumn (or it was, it has been fixed). Agreed it doesn't use
a CounterMutation but given the test, why should it bother.
                
> Tests write CounterUpdateColumns 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
>         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.
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

        

Mime
View raw message