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 AA0CF9D1D for ; Mon, 4 Jun 2012 18:05:16 +0000 (UTC) Received: (qmail 6642 invoked by uid 500); 4 Jun 2012 18:05:14 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 6614 invoked by uid 500); 4 Jun 2012 18:05:14 -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 6605 invoked by uid 99); 4 Jun 2012 18:05:14 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Jun 2012 18:05:14 +0000 X-ASF-Spam-Status: No, hits=-5.0 required=5.0 tests=RCVD_IN_DNSWL_HI,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of prvs=4958a05ce=bburruss@expedia.com designates 216.251.112.223 as permitted sender) Received: from [216.251.112.223] (HELO mx1b.expedia.com) (216.251.112.223) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Jun 2012 18:05:08 +0000 X-SRBS: None X-HAT: Sender Group RELAYLIST, Policy $RELAYED applied. Received: from unknown (HELO CHC-EXCHNA01.SEA.CORP.EXPECN.COM) ([10.184.69.25]) by mx1b.sea.corp.expecn.com with ESMTP; 04 Jun 2012 11:04:46 -0700 Received: from CHC-CCR02.SEA.CORP.EXPECN.COM ([10.184.69.23]) by CHC-EXCHNA01.SEA.CORP.EXPECN.COM ([10.184.69.25]) with mapi; Mon, 4 Jun 2012 11:04:46 -0700 From: Todd Burruss To: "user@cassandra.apache.org" Date: Mon, 4 Jun 2012 11:05:20 -0700 Subject: Re: batch isolation Thread-Topic: batch isolation Thread-Index: Ac1CfIX5aU4MAOuWQ3a5LJTntcoBbA== Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.2.120421 acceptlanguage: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 I don't think I'm being clear. I just was wondering if a "row delete" is isolated with all the other inserts or deletes to a specific column family and key in the same batch. On 6/4/12 1:58 AM, "Sylvain Lebresne" wrote: >On Sun, Jun 3, 2012 at 6:05 PM, Todd Burruss wrote: >> I just meant there is a "row delete" in the same batch as inserts - all >>to >> the same column family and key > >Then it's the timestamp that will decide what happens. Whatever has a >timestamp lower or equal to the tombstone timestamp will be deleted >(that stands for insert in the batch itself). > >-- >Sylvain > > >> >> >> -----Original Message----- >> From: Sylvain Lebresne [sylvain@datastax.com] >> Received: Sunday, 03 Jun 2012, 3:44am >> To: user@cassandra.apache.org [user@cassandra.apache.org] >> Subject: Re: batch isolation >> >> On Sun, Jun 3, 2012 at 2:53 AM, Todd Burruss >>wrote:> >>> 1 =AD does this mean that a batch_mutate that first sends a "row delete= " >>> mutation on key X, then subsequent insert mutations for key X is >>>isolated? >> >> I'm not sure what you mean by having "a batch_mutate that first sends >> ... then ...", since a batch_mutate is a single API call. >> >>> 2 =AD does isolation span column families for the same key within the >>>same >>> batch_mutate? >> >> No, it doesn't span column families (contrarily to atomicity). There >> is more details in >> http://www.datastax.com/dev/blog/row-level-isolation. >> >> -- >> Sylvain