[
https://issues.apache.org/jira/browse/CASSANDRA-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12905202#action_12905202
]
Johan Oskarsson commented on CASSANDRA-1072:
--------------------------------------------
We've been looking at ways to adjust this patch to meet the EC concern above
and came up with this compromise: a new increment method in the thrift
interface.
With a new method Cassandra users would not be confused by the slightly
different ConsistencyLevel behavior in the current patch. The method name and
parameters would be a clear indication as to what it does and separate it from
the methods used on standard column families.
With the interest shown in this feature I hope we can reach a compromise that
works for all involved.
> 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, 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.
