Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <21812663.155511277999749835.JavaMail.jira@thor>
Date: Thu, 1 Jul 2010 11:55:49 -0400 (EDT)
From: "Kelvin Kakugawa (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Commented: (CASSANDRA-1243) Break out context code from
 increment counters
In-Reply-To: <3250197.145731277947910060.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kelvin Kakugawa commented on CASSANDRA-1243:
--------------------------------------------

In 1072, I've already worked out the logic to extend counter contexts w/ bit flags and perform secondary counter writes in SP.mutateBlocking().  Still needs to be tested, though.

After the above changeset is vetted, we should go through and start removing all the "clean"-related logic.  None of us were fans of that logic, either, and it'll definitely reduce the size of this patch against trunk.

> Break out context code from increment counters
> ----------------------------------------------
>
>                 Key: CASSANDRA-1243
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1243
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: Core
>            Reporter: Johan Oskarsson
>         Attachments: CASSANDRA-1243.patch, CASSANDRA-1243.patch
>
>
> In order to make CASSANDRA-1072 easier to digest we should split out context related functionality and prepare the code base for multiple clock types. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.