Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of stoffe@gmail.com designates
 209.85.192.181 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CALte62wNDvzbFrLGmw2L2qNY+oFh=rFGKe8diSFA-V6Hy0UGzg@mail.gmail.com>
References: 
 <CADSBNAhzYx0o54c8082WQP-nwnTXjTsQU9y4XqXPmSSh89PE+w@mail.gmail.com>
	<CALte62yRKoGsPC_bCd0omYmSvwESLPYWvg=mg4iCXcpC+dDi2w@mail.gmail.com>
	<CADSBNAhnRQJQ1j4f2j2WH4KEy=4zk9x8Bu2rUUVfjON++9L34w@mail.gmail.com>
	<CAB7cnggLfCmO12TOayZ1SrtY01KnBnVpqNd06B0V_Qy5G2eShQ@mail.gmail.com>
	<CAB7cnghrduc=-EsmOJyBg3xLd03uzO22rWicB8R+8NB_K2_OPA@mail.gmail.com>
	<CAB7cngjzhd+6yAdy2Kqv0_buVSpR6MUG8Euuyd3j=G0N+a2sYQ@mail.gmail.com>
	<CALte62wNDvzbFrLGmw2L2qNY+oFh=rFGKe8diSFA-V6Hy0UGzg@mail.gmail.com>
Date: Sat, 20 Apr 2013 09:17:01 +0200
Message-ID: 
 <CADSBNAhRQfdv5AhiWC4xyz-2A0BLXvcTjQekOHCBpEn2z+aB2A@mail.gmail.com>
Subject: Re: Overwrite a row
From: =?ISO-8859-1?Q?Kristoffer_Sj=F6gren?= <stoffe@gmail.com>
To: user@hbase.apache.org
Content-Type: multipart/alternative; boundary=bcaec5431b80358c2b04dac59f4b

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

The schema is known beforehand so this is exactly what I need. Great!

One more question. What guarantees does the batch operation have? Are the
operations contained within each batch atomic? I.e. all mutations will be
given the same timestamp? If something fails, all operation fail or can it
fail partially?

Thanks for your help, much appreciated.

Cheers,
-Kristoffer


On Sat, Apr 20, 2013 at 4:47 AM, Ted Yu <yuzhihong@gmail.com> wrote:

> I don't know details about Kristoffer's schema.
> If all the column qualifiers are known a priori, mutateRow() should serve
> his needs.
>
> HBase allows arbitrary number of columns in a column family. If the schem=
a
> is dynamic, mutateRow() wouldn't suffice.
> If the column qualifiers are known but the row is very wide (and a few
> columns are updated per call), performance would degrade.
>
> Just some factors to consider.
>
> Cheers
>
> On Fri, Apr 19, 2013 at 1:41 PM, Mohamed Ibrahim <mibrahim@mibrahim.net
> >wrote:
>
> > Actually I do see it in the 0.94 JavaDocs (
> >
> >
> http://hbase.apache.org/0.94/apidocs/org/apache/hadoop/hbase/client/HTabl=
e.html#mutateRow(org.apache.hadoop.hbase.client.RowMutations)
> > ),
> > so may be it was added in 0.94.6 even though the jira says fixed in 0.9=
5
> .
> > I haven't used it though, but it seems that's what you're looking for.
> >
> > Sorry for confusion.
> >
> > Mohamed
> >
> >
> > On Fri, Apr 19, 2013 at 4:35 PM, Mohamed Ibrahim <mibrahim@mibrahim.net
> > >wrote:
> >
> > > It seems that 0.95 is not released yet, mutateRow won't be a solution
> for
> > > now. I saw it in the downloads and I thought it was released.
> > >
> > >
> > > On Fri, Apr 19, 2013 at 4:18 PM, Mohamed Ibrahim <
> mibrahim@mibrahim.net
> > >wrote:
> > >
> > >> Just noticed you want to delete as well. I think that's supported
> since
> > >> 0.95 in mutateRow (
> > >>
> >
> http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/HTable.htm=
l#mutateRow(org.apache.hadoop.hbase.client.RowMutations)
> ).
> > >> You can do multiple puts and deletes and they will be performed
> > atomically.
> > >> So you can remove qualifiers and put new ones.
> > >>
> > >> Mohamed
> > >>
> > >>
> > >> On Fri, Apr 19, 2013 at 3:44 PM, Kristoffer Sj=F6gren <stoffe@gmail.=
com
> > >wrote:
> > >>
> > >>> What would you suggest? I want the operation to be atomic.
> > >>>
> > >>>
> > >>> On Fri, Apr 19, 2013 at 8:32 PM, Ted Yu <yuzhihong@gmail.com> wrote=
:
> > >>>
> > >>> > What is the maximum number of versions do you allow for the
> > underlying
> > >>> > table ?
> > >>> >
> > >>> > Thanks
> > >>> >
> > >>> > On Fri, Apr 19, 2013 at 10:53 AM, Kristoffer Sj=F6gren <
> > stoffe@gmail.com
> > >>> > >wrote:
> > >>> >
> > >>> > > Hi
> > >>> > >
> > >>> > > Is it possible to completely overwrite/replace a row in a singl=
e
> > >>> _atomic_
> > >>> > > action? Already existing columns and qualifiers should be remov=
ed
> > if
> > >>> they
> > >>> > > do not exist in the data inserted into the row.
> > >>> > >
> > >>> > > The only way to do this is to first delete the row then insert
> new
> > >>> data
> > >>> > in
> > >>> > > its place, correct? Or is there an operation to do this?
> > >>> > >
> > >>> > > Cheers,
> > >>> > > -Kristoffer
> > >>> > >
> > >>> >
> > >>>
> > >>
> > >>
> > >
> >
>

--bcaec5431b80358c2b04dac59f4b--