cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Johan Oskarsson (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CASSANDRA-1072) Increment counters
Date Thu, 24 Jun 2010 22:13:54 GMT

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

Johan Oskarsson updated CASSANDRA-1072:
---------------------------------------

    Attachment: CASSANDRA-1072.patch

This updated patch addresses most concerns in the review, with the exception of the replication
logic that Kelvin is working on.

* Check for invalid/negative input. Includes unit test.
* Pick the correct timestamp in updateDeleteTimestamp, added unit test
* Collapsed duplicate AES code into one
* Clarified IncrementCounterReconciler.reconcile() code
* IncrementCountContext.merge() refactor as suggested
* Removed dead code in Column
* IncrementCounterContext.diff() reformat
* Removed TimestampClock constructor


> Increment counters
> ------------------
>
>                 Key: CASSANDRA-1072
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1072
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: Core
>            Reporter: Johan Oskarsson
>            Assignee: Kelvin Kakugawa
>         Attachments: CASSANDRA-1072-2.patch, CASSANDRA-1072.patch, CASSANDRA-1072.patch
>
>
> Break out the increment counters out of CASSANDRA-580. Classes are shared between the
two features but without the plain version vector code the changeset becomes smaller and more
manageable.

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


Mime
View raw message