Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-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 2C7FD9188 for ; Tue, 22 May 2012 18:31:19 +0000 (UTC) Received: (qmail 9193 invoked by uid 500); 22 May 2012 18:31:17 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 9113 invoked by uid 500); 22 May 2012 18:31:17 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 9104 invoked by uid 99); 22 May 2012 18:31:17 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 May 2012 18:31:17 +0000 X-ASF-Spam-Status: No, hits=-0.5 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of tombrown52@gmail.com designates 209.85.220.169 as permitted sender) Received: from [209.85.220.169] (HELO mail-vc0-f169.google.com) (209.85.220.169) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 May 2012 18:31:09 +0000 Received: by vcbfl10 with SMTP id fl10so1082529vcb.14 for ; Tue, 22 May 2012 11:30:48 -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=89+hR38PJCA8WZ89tyZyC7YQUGnkHgbGQBBIKbe7vaY=; b=B7nPZuX7Be2BuVdLyb/5/dsdjxEsivERd1JdgwQ+VOMzxbPpjAcy9Wp6I2mfqlLzGN CsUOWhTnHzEhjf+EwZWVu8rB8NNgShDJvOfk7zwylwl4WYScMQCtzBF7fm+XfKQ/ZgEx N9PAVjJCwb0m+jM+HS0Eo0GsdvV/DZBBR0tKX3VPXYxYy4LBntKdgFEZdZ8/Fkhexdm8 nZVE5KYkeXVTg+1LY2LssjLTYCPy8yLwuHWEA0pBSZ7+YsXtMwl4Z9hOiY41D8fOmY/o ZsQP9Ao3AUY7CcCGXIggz50L+W4SLlObSF53sI8DKyb51g+pAzc/nVHZt1eL2IjKD/WI 9OLw== MIME-Version: 1.0 Received: by 10.52.29.45 with SMTP id g13mr6314993vdh.10.1337711448191; Tue, 22 May 2012 11:30:48 -0700 (PDT) Received: by 10.52.27.44 with HTTP; Tue, 22 May 2012 11:30:48 -0700 (PDT) In-Reply-To: References: Date: Tue, 22 May 2012 12:30:48 -0600 Message-ID: Subject: Re: Using put for nullifying qualifiers From: Tom Brown To: user@hbase.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I don't think you can include a delete with a put and keep it atomic. You could include a null version of the column with your put, though, for a similar effect. --Tom On Tue, May 22, 2012 at 10:55 AM, Kristoffer Sj=F6gren w= rote: > Hi > > I'm trying to use Put operations to replace ("set") already existing rows > by nullify certain columns and qualifiers as part of an Put operation. > > The reason I want to do this is 1) keep the operation atomic/consistent 2= ) > avoid latency from first doing Delete then Put. > > Is there some way to do this kind of operation? > > Cheers, > -Kristoffer