cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kelvin Kakugawa (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CASSANDRA-1072) Increment counters
Date Wed, 15 Dec 2010 19:36:12 GMT

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

Kelvin Kakugawa updated CASSANDRA-1072:
---------------------------------------

    Comment: was deleted

(was: I was looking through the code and thought about it more.

We can't remove value ser/des, because we need to serialize it for the commit log (and hinted
hand-off).  So, value needs to be serialized, at some point.  So, the disk format won't change.

However, we can optimize the code to not recalculate the total on every update w/o read. 
Looking into this.)

> 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.121310.patch, CASSANDRA-1072.patch, increment_test.py,
Partitionedcountersdesigndoc.pdf
>
>
> 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