Return-Path: 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 4B5FB9BDB for ; Wed, 14 Mar 2012 22:22:30 +0000 (UTC) Received: (qmail 98650 invoked by uid 500); 14 Mar 2012 22:22:28 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 98629 invoked by uid 500); 14 Mar 2012 22:22:28 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 98621 invoked by uid 99); 14 Mar 2012 22:22:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Mar 2012 22:22:28 +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 (athena.apache.org: domain of s5alye@gmail.com designates 209.85.213.43 as permitted sender) Received: from [209.85.213.43] (HELO mail-yw0-f43.google.com) (209.85.213.43) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Mar 2012 22:22:23 +0000 Received: by yhkk6 with SMTP id k6so2939224yhk.30 for ; Wed, 14 Mar 2012 15:22:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=l5PhXMOeG9WfqE833kEEOBd344lx/rP2yAmLEcQypMo=; b=qS8KviH9ZmSuXTK8x8gP8kj/lpI3J5h6HrX6kVQg7q16nk0lI+mrgtakOmrL3MVdft yK3s7wH7VZD0ml5BHp3cD8AtLbH3I7sWCw1QPfm7Ta/lWMY7k4VHVjywnjsmQ0M4+Asu 2TrI7XDciJQbIFOw0tQa3WOsqlVSg5bhnGKxBIBCLds7w4lKWQc5EQqLIEjqNKNTefSl TcI7ukNGs+FKR4yHySTo4HU2Izd/EivunBe787ZKpu1keHWcvN3Lawg8DbqsHiTi9I5H W1PDOfRjSiz55HEmZFH2VOaK34kfJwxFK7kpNHszDyvWo7T1enAayXyCI5lAywyUCBmA /j7w== MIME-Version: 1.0 Received: by 10.60.4.170 with SMTP id l10mr5445645oel.67.1331763722024; Wed, 14 Mar 2012 15:22:02 -0700 (PDT) Received: by 10.182.91.165 with HTTP; Wed, 14 Mar 2012 15:22:01 -0700 (PDT) In-Reply-To: References: Date: Wed, 14 Mar 2012 18:22:01 -0400 Message-ID: Subject: Re: Does the 'batch' order matter ? From: A J To: user@cassandra.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org > No, batch_mutate() is an atomic operation. When a node locally applies a= batch mutation, either all of the changes are applied or none of them are.= < The steps in my batch are not confined to a single CF, nor to a single key. The documentation says: datastax: Column updates are only considered atomic within a given record (row). Pycassa.batch: This interface does not implement atomic operations across column families. All the limitations of the batch_mutate Thrift API call applies. Remember, a mutation in Cassandra is always atomic per key per column family only. On Wed, Mar 14, 2012 at 4:15 PM, Tyler Hobbs wrote: > On Wed, Mar 14, 2012 at 11:50 AM, A J wrote: >> >> >> Are you saying the way 'batch mutate' is coded, the order of writes in >> the batch does not mean anything ? You can ask the batch to do A,B,C >> and then D in sequence; but sometimes Cassandra can end up applying >> just C and A,B (and D) may still not be applied ? > > > No, batch_mutate() is an atomic operation.=A0 When a node locally applies= a > batch mutation, either all of the changes are applied or none of them are= . > > Aaron was referring to the possibility that one of the replicas received = the > batch_mutate, but the other replicas did not. > > -- > Tyler Hobbs > DataStax >