Mailing-List: contact hbase-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-user@hadoop.apache.org
Received-SPF: pass (athena.apache.org: domain of bradfordstephens@gmail.com
 designates 209.85.211.198 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=Ukht2jVIzHfAMQAYN8sP7ZxuXkZkiXeZhrGgOirKgdYGh+BnN9uLRvO0Vd81qhZJvU
         kP04mmHkwK4VHSQKEsoWhD56ulZldxi845B4JjOXb6Zf4os5mAU+NWroDJtEj5lwoHbR
         AKnXa44f5F7Nb+xzxYJPFjpJnOlu6piGCBePo=
MIME-Version: 1.0
In-Reply-To: <4A8985A0.3060207@streamy.com>
References: <a55deab80908162351p7c24b6f0ue9fb25c23ff94f95@mail.gmail.com>
	 <78568af10908162358t57f2ab2fi25a4491065fcbf6f@mail.gmail.com>
	 <a55deab80908170855p48c1f52bm5d254fb8a0bd9f2d@mail.gmail.com>
	 <4A8985A0.3060207@streamy.com>
Date: Mon, 17 Aug 2009 12:24:14 -0700
Message-ID: <860544ed0908171224o41cdf9fj7482409bb99375c0@mail.gmail.com>
Subject: Re: Hi, i am still puzzeld to find a row key by a cell.
From: Bradford Stephens <bradfordstephens@gmail.com>
To: hbase-user@hadoop.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Just reiterating with JGray says -- usually, when you need a secondary
index, you can get away with denormalizing and duplicating your data.

On Mon, Aug 17, 2009 at 9:30 AM, Jonathan Gray<jlist@streamy.com> wrote:
> This is possible by checking the values in your client, through server-si=
de
> filters (see org.apache.hadoop.hbase.filter), or with secondary indexing =
(as
> described in my previous e-mail).
>
> In the first two cases, you are doing a full table scan so it is very
> inefficient. =A0That's the same as it would be in an RDBMS if you were no=
t
> using secondary indexes, however.
>
> HBase has limited secondary indexing support, but do not expect the
> flexibility and performance you get from an RDBMS secondary index.
>
> If this is central to your usage of HBase, make sure that HBase is what y=
ou
> want and take another look at your schema to see if there might be a bett=
er
> design to prevent needing heavy indexing or table scanning.
>
> JG
>
> Rocks wrote:
>>
>> Thanks for you answer.
>> however, what i want to do just likes "where" keyword of SQL in RDBMS. I=
s
>> it impossible in hbase ?
>>
>> On Mon, Aug 17, 2009 at 2:58 PM, Ryan Rawson <ryanobjc@gmail.com> wrote:
>>
>>> hey,
>>>
>>> That isn't how hbase (or even rdbms) work. =A0Instead you can retrieve
>>> rows based on their row key. Otherwise you will have to read the
>>> entire table to find just that 1 row. Yes this is as inefficient as it
>>> sounds.
>>>
>>> If you frequently have this issue, you may need to build and maintain
>>> secondary indexes. Unlike relational dbs, there is no built in support
>>> for this, you have to write your app to handle this.
>>>
>>> -yran
>>>
>>>
>>>
>>> On Sun, Aug 16, 2009 at 11:51 PM, lei wang<hbasemaillist@gmail.com>
>>> wrote:
>>>>
>>>> Hi, if a know a cell in a hbase for its column:<qualifer>:value, =A0i =
need
>>>
>>> to
>>>>
>>>> know which row key it belongs to. I searched the HBase api several
>>>> times,
>>>> but i can not find the right method to solve my problem. Thanks for
>>>> one's
>>>> suggestion to me.
>>>>
>>
>


--=20
http://www.roadtofailure.com -- The Fringes of Scalability, Social
Media, and Computer Science