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 michael_segel@hotmail.com
 designates 65.55.111.90 as permitted sender)
Message-ID: <BLU0-SMTP165A879F95A0A89714CD86E8F560@phx.gbl>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Why only check1-and-putMany and check1-and-deleteMany?
From: Michael Segel <michael_segel@hotmail.com>
In-Reply-To: 
 <OFFF42D471.F369174E-ON85257ABB.0059647C-85257ABB.0059AEC7@us.ibm.com>
Date: Mon, 19 Nov 2012 10:50:28 -0600
Content-Transfer-Encoding: quoted-printable
References: 
 <OF59FB7313.E5932172-ON85257ABA.00128EF9-85257ABA.001340C9@us.ibm.com>
 <CALte62ytHeMK4SUnKv733OG=cu+hmoK8z58uhD-i-vy3YMdAsw@mail.gmail.com>
 <OF8943AB2E.C6468F03-ON85257ABA.00233B7A-85257ABA.00238938@us.ibm.com>
 <BLU0-SMTP12358539AB60066B86B14D58F570@phx.gbl>
 <OFFF42D471.F369174E-ON85257ABB.0059647C-85257ABB.0059AEC7@us.ibm.com>
To: user@hbase.apache.org

Mike,=20

What I am asking is how you define an append in a system that doesn't =
support appends.=20

I'm trying to understand what it is that you wish to achieve.=20

To give you an answer which you will probably not like... HBase is still =
very primitive in terms of a full feature functionality.=20


On Nov 19, 2012, at 10:19 AM, Mike Spreitzer <mspreitz@us.ibm.com> =
wrote:

> If you are asking why the HBase API has appends as well as puts, I am =
not=20
> going to play the expert here.  Either there is a good reason for it, =
or=20
> not.
>=20
> My goal in this line of questioning is to understand why there is not =
a=20
> more comprehensive composite atomic operation available.  If there is =
a=20
> good reason for the API to include appends, then that reason applies =
here.=20
> If there is no such reason, then you may ignore the appends in my=20
> question.
>=20
> Thanks,
> Mike
>=20
>=20
>=20
> From:   Michael Segel <michael_segel@hotmail.com>
> To:     user@hbase.apache.org
> Date:   11/18/2012 03:15 PM
> Subject:        Re: Why only check1-and-putMany and =
check1-and-deleteMany?
>=20
>=20
>=20
> Ok, maybe this is a silly question on my part....=20
>=20
> Could you define what you mean by check and append?=20
> With respect to HBase, how would that be different from check and put?=20=

>=20
>=20
> On Nov 18, 2012, at 12:28 AM, Mike Spreitzer <mspreitz@us.ibm.com> =
wrote:
>=20
>> I am not looking at the trunk.  I am just a user looking at the=20
> interface=20
>> documented on the web site and wondering why the atomic composite=20
>> functionality is so limited.  It is not hard to imagine an expanded=20=

>> interface that allows checking an arbitrary set of columns and, if =
each=20
>> has a value specified for it, doing an arbitrary set of Mutations.
>>=20
>> Thanks,
>> Mike
>>=20
>>=20
>>=20
>> From:   Ted Yu <yuzhihong@gmail.com>
>> To:     user@hbase.apache.org
>> Date:   11/17/2012 11:44 PM
>> Subject:        Re: Why only check1-and-putMany and=20
> check1-and-deleteMany?
>>=20
>>=20
>>=20
>> Are you looking at trunk code ?
>>=20
>> In trunk, take a look at HRegion.checkAndMutate() where you can =
specify
>> ByteArrayComparable which does the comparison (matching).
>> There is still the limit of single value:
>>       } else if (result.size() =3D=3D 1 && !valueIsNull) {
>>         KeyValue kv =3D result.get(0);
>>=20
>> For the moment, only Put and Delete are supported:
>>=20
>>   if (!isPut && !(w instanceof Delete))
>>     throw new DoNotRetryIOException("Action must be Put or Delete");
>> If you have suggestion on how the check part can be more general, =
please
>> comment.
>>=20
>> Thanks
>>=20
>> On Sat, Nov 17, 2012 at 7:30 PM, Mike Spreitzer <mspreitz@us.ibm.com>=20=

>> wrote:
>>=20
>>> If I understand correctly, an HTable has two composite atomic=20
>> operations,
>>> checkAndPut and checkAndDelete.  The check part checks just a single
>>> column's value.  Why not allow checking more than one column?
>>>=20
>>> Why no checkAndAppend?
>>>=20
>>> The checkAndPut operation can put to multiple columns, right?  And =
the
>>> checkAndDelete operation can delete multiple columns, right?  Why =
not=20
>> let
>>> them be mixed?  Why not checkAndMutate?
>>>=20
>>> Thanks!
>>> Mike
>>=20
>=20
>=20