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] Commented: (CASSANDRA-1072) Increment counters
Date Tue, 14 Sep 2010 13:33:46 GMT

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

Johan Oskarsson commented on CASSANDRA-1072:
--------------------------------------------

The clock changes are separate from the counters and were introduced in a different ticket,
CASSANDRA-1070. I see no reason to add more work that is not directly related to counters
in this jira. The clock changes would get into trunk quicker if we didn't, avoiding the extra
overhead of a big patch during reviews, merge with trunk, code updates and publication of
a new patch.
If the concern is that we won't attend to the clocks once this patch is in I can promise that
we'll look at it straight away.

> 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-2.patch, CASSANDRA-1072.patch,
Incrementcountersdesigndoc.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