Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of stoffe@gmail.com designates
 209.85.213.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAHtRq2cqvgG9ZBekY8r5LKbc9FT806jiFKegu2xq-BrRUkBOjw@mail.gmail.com>
References: 
 <CADSBNAheVBm+7otokg6_uJrLBwuQWuBSSJ6YAyO3Rg+NyaxzUg@mail.gmail.com>
	<CAHtRq2cqvgG9ZBekY8r5LKbc9FT806jiFKegu2xq-BrRUkBOjw@mail.gmail.com>
Date: Tue, 22 May 2012 22:22:43 +0200
Message-ID: 
 <CADSBNAjO=+bve6GPbM2DfyyqCS9FfkbA55cUXF2-dMeZYLoNyQ@mail.gmail.com>
Subject: Re: Using put for nullifying qualifiers
From: =?ISO-8859-1?Q?Kristoffer_Sj=F6gren?= <stoffe@gmail.com>
To: user@hbase.apache.org
Content-Type: multipart/alternative; boundary=e89a8f3ba309ef7a1c04c0a5c773

--e89a8f3ba309ef7a1c04c0a5c773
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Thanks, sounds like that should do it.

So im guessing it is correct to assume that _all_ KeyValues added to a
_single_ Put operation will either wholely succeed or wholely fail as long
as they belong to the same row?

On Tue, May 22, 2012 at 8:30 PM, Tom Brown <tombrown52@gmail.com> wrote:

> 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 <stoffe@gmail.com>
> wrote:
> > Hi
> >
> > I'm trying to use Put operations to replace ("set") already existing ro=
ws
> > 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
>

--e89a8f3ba309ef7a1c04c0a5c773--