cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1072) Increment counters
Date Sun, 18 Jul 2010 23:45:54 GMT

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

Jonathan Ellis commented on CASSANDRA-1072:
-------------------------------------------

As commented above, I need help understanding why this is necessary:

+            /**
+             * perform secondary writes, if necessary
+             *
+             * use case: support distributed counter writes for CL > ONE
+             * rationale:
+             *   distributed counters need to be first written to one replica
+             *     to be correctly accounted for
+             *   then, for CL > ONE, writes can be sent to other replicas
+             *     to help them catch up to the total count of the first replica
+             */

Is that what you mean by "the replication logic that Kelvin is working on?"

> 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
>
>
> 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