Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Received-SPF: pass (google.com: domain of tvinod@socialyantra.com designates
 10.180.80.226 as permitted sender) client-ip=10.180.80.226;
MIME-Version: 1.0
Sender: tvinod@socialyantra.com
In-Reply-To: 
 <CALte62wMFsvEcQwRbse7HiR4AUGFtFJ3ynvH2z7gpT=oD1py5A@mail.gmail.com>
References: 
 <CAKnDEhjNuCs+p=fwriTJB8XWRGfz-gWdVnoxbm1pOj69Nwdrrw@mail.gmail.com>
	<CALte62wMFsvEcQwRbse7HiR4AUGFtFJ3ynvH2z7gpT=oD1py5A@mail.gmail.com>
Date: Wed, 22 Feb 2012 09:35:22 -0800
Message-ID: 
 <CAHau4ysxA7rb9zPZnEAFa8=rdcu=E1G5aNNovnAPusQgH0nq6w@mail.gmail.com>
Subject: Re: Solr & HBase - Re: How is Data Indexed in HBase?
From: T Vinod Gupta <tvinod@readypulse.com>
To: user@hbase.apache.org
Cc: bing.li@asu.edu, Jacques <whshub@gmail.com>, hbase-user@hadoop.apache.org
Content-Type: multipart/alternative; boundary=f46d044288d2c0df4f04b990f3cd

--f46d044288d2c0df4f04b990f3cd
Content-Type: text/plain; charset=ISO-8859-1

Bing,
Its a classic battle on whether to use solr or hbase or a combination of
both. both systems are very different but there is some overlap in the
utility. they also differ vastly when it compares to computation power,
storage needs, etc. so in the end, it all boils down to your use case. you
need to pick the technology that it best suited to your needs.
im still not clear on your use case though.

btw, if you haven't started using solr yet - then you might want to
checkout ElasticSearch. I spent over a week researching between solr and ES
and eventually chose ES due to its cool merits.

thanks

On Wed, Feb 22, 2012 at 9:31 AM, Ted Yu <yuzhihong@gmail.com> wrote:

> There is no secondary index support in HBase at the moment.
>
> It's on our road map.
>
> FYI
>
> On Wed, Feb 22, 2012 at 9:28 AM, Bing Li <lblabs@gmail.com> wrote:
>
> > Jacques,
> >
> > Yes. But I still have questions about that.
> >
> > In my system, when users search with a keyword arbitrarily, the query is
> > forwarded to Solr. No any updating operations but appending new indexes
> > exist in Solr managed data.
> >
> > When I need to retrieve data based on ranking values, HBase is used. And,
> > the ranking values need to be updated all the time.
> >
> > Is that correct?
> >
> > My question is that the performance must be low if keeping consistency
> in a
> > large scale distributed environment. How does HBase handle this issue?
> >
> > Thanks so much!
> >
> > Bing
> >
> >
> > On Thu, Feb 23, 2012 at 1:17 AM, Jacques <whshub@gmail.com> wrote:
> >
> > > It is highly unlikely that you could replace Solr with HBase.  They're
> > > really apples and oranges.
> > >
> > >
> > > On Wed, Feb 22, 2012 at 1:09 AM, Bing Li <lblabs@gmail.com> wrote:
> > >
> > >> Dear all,
> > >>
> > >> I wonder how data in HBase is indexed? Now Solr is used in my system
> > >> because data is managed in inverted index. Such an index is suitable
> to
> > >> retrieve unstructured and huge amount of data. How does HBase deal
> with
> > >> the
> > >> issue? May I replaced Solr with HBase?
> > >>
> > >> Thanks so much!
> > >>
> > >> Best regards,
> > >> Bing
> > >>
> > >
> > >
> >
>

--f46d044288d2c0df4f04b990f3cd--