Return-Path: 
 <user-return-42711-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org>
X-Original-To: apmail-cassandra-user-archive@www.apache.org
Delivered-To: apmail-cassandra-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 6AB6911591
	for <apmail-cassandra-user-archive@www.apache.org>;
 Tue,  9 Sep 2014 21:37:11 +0000 (UTC)
Received: (qmail 6710 invoked by uid 500); 9 Sep 2014 21:37:09 -0000
Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org
Received: (qmail 6678 invoked by uid 500); 9 Sep 2014 21:37:09 -0000
Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@cassandra.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@cassandra.apache.org>
List-Post: <mailto:user@cassandra.apache.org>
List-Id: <user.cassandra.apache.org>
Reply-To: user@cassandra.apache.org
Delivered-To: mailing list user@cassandra.apache.org
Received: (qmail 6668 invoked by uid 99); 9 Sep 2014 21:37:08 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Sep 2014 21:37:08 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of viy.net@gmail.com designates
 209.85.217.177 as permitted sender)
Received: from [209.85.217.177] (HELO mail-lb0-f177.google.com)
 (209.85.217.177)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Sep 2014 21:36:43 +0000
Received: by mail-lb0-f177.google.com with SMTP id l4so6873601lbv.22
        for <user@cassandra.apache.org>; Tue, 09 Sep 2014 14:36:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=message-id:date:from:user-agent:mime-version:to:subject
         :content-type:content-transfer-encoding;
        bh=dSkBFCx57Us08DvomUBjldKY85HRvGtpOAGKy01Aw1U=;
        b=UZjUiCsAGs4HsUcVgtAd4awF3Y9aPoL3EPEa+UNth3qD1QvPdcceZSUr35/jswb/p4
         M8c2IRPSsWfiRRXHd6dlk/qW9cZ2mS2rX83TfidKqdAkjwRzYAkx3kZedpfiKd0apCcj
         Jg8gsswhR0TNq2tnOU6uMFNX5UtoDS6xeYKfz9DKx0iYYQR9xunouT8xu+tt0N2yJ20x
         fJOxgdsaUJsarVorxOT+khgLsFgeSqDePmXuOZCDcVEDdHWM6NrU95cIarDDlONeYL1N
         DFu44M4+b6apbhTvX2wqwBHnhXjean1HH42ysovF+moBlGk3RcboaMGyjEWhWxuwcSPB
         E7vQ==
X-Received: by 10.152.45.42 with SMTP id j10mr5382440lam.91.1410298602453;
        Tue, 09 Sep 2014 14:36:42 -0700 (PDT)
Received: from [192.168.0.218] ([91.214.131.110])
        by mx.google.com with ESMTPSA id v1sm4655236lag.19.2014.09.09.14.36.41
        for <user@cassandra.apache.org>
        (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Tue, 09 Sep 2014 14:36:41 -0700 (PDT)
Message-ID: <540F72EA.2030604@gmail.com>
Date: Wed, 10 Sep 2014 01:36:42 +0400
From: Eugene Voytitsky <viy.net@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
 rv:31.0) Gecko/20100101 Thunderbird/31.1.0
MIME-Version: 1.0
To: user@cassandra.apache.org
Subject: Atomic batch of counters in Cassandra 2.1
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

As I understand, atomic batch for counters can't work correctly 
(atomically) prior to 2.1 because of counters implementation.
[Link: http://www.datastax.com/dev/blog/atomic-batches-in-cassandra-1-2]

Cassandra 2.1. reimplements the counters.

Will atomic batch of counters work as expected (atomically) in Cassandra 
2.1?

-- 
Best regards,
Eugene Voytitsky