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 Wed, 24 Nov 2010 04:29:23 GMT

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

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

We want to help, I'm just thinking this through.

It sounds like you agree that using UUIDs is the right approach long term.  (Lots of people
run Cassandra on EC2 + EBS, so changing IPs the data is on is not a corner case at all there.
 Or any time you restore from a snapshot...)

So if you're going to be running this patch indefinitely, is committing it knowing that we're
going to fix it to use UUIDs incompatibly, actually useful to the "get Twitter running mainline
Cassandra" goal?

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