Return-Path: Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: (qmail 26535 invoked from network); 1 Sep 2010 20:23:22 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 1 Sep 2010 20:23:22 -0000 Received: (qmail 69877 invoked by uid 500); 1 Sep 2010 20:23:22 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 69781 invoked by uid 500); 1 Sep 2010 20:23:22 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 69773 invoked by uid 99); 1 Sep 2010 20:23:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Sep 2010 20:23:21 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Sep 2010 20:23:21 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o81KN1kL019215 for ; Wed, 1 Sep 2010 20:23:01 GMT Message-ID: <11676227.122731283372581029.JavaMail.jira@thor> Date: Wed, 1 Sep 2010 16:23:01 -0400 (EDT) From: "Johan Oskarsson (JIRA)" To: commits@cassandra.apache.org Subject: [jira] Commented: (CASSANDRA-1072) Increment counters In-Reply-To: <27538947.141273514791054.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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.