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 Mon, 06 Dec 2010 23:16:21 GMT

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

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

bq. CounterMutation is a struct w/ 2 optional fields: Counter, and Deletion

looks reasonable to me.

bq. Not in favor of CounterDeletion w/o a timestamp

I think it's confusing from a user's perspective to have it required on delete when it is
not on write.  If there's no value to letting the user provide timestamps other than the current
time then let's leave it out.

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