Dear Mr Gupta,
Your understanding about my solution is correct. Now both HBase and Solr
are used in my system. I hope it could work.
Thanks so much for your reply!
Best regards,
Bing
On Fri, Feb 24, 2012 at 3:30 AM, T Vinod Gupta wrote:
> regarding your question on hbase support for high perfo
regarding your question on hbase support for high performance and
consistency - i would say hbase is highly scalable and performant. how it
does what it does can be understood by reading relevant chapters around
architecture and design in the hbase book.
with regards to ranking, i see your problem
sage -
> From: Andrew Purtell
> To: "user@hbase.apache.org"
> Cc: "hbase-u...@hadoop.apache.org"
> Sent: Thursday, February 23, 2012 11:22 AM
> Subject: Re: Solr & HBase - Re: How is Data Indexed in HBase?
>
> I'd also make a comment on this:
&g
sday, February 22, 2012 10:18 AM
> Subject: Re: Solr & HBase - Re: How is Data Indexed in HBase?
>
> One minor clarification:
>
> HBase is primarily built for retrieving a single row at a time based on a
> predetermined and known location (the key).
>
> Substitute tha
One minor clarification:
HBase is primarily built for retrieving a single row at a time based on a
predetermined and known location (the key).
Substitute that with: "HBase is primarily built for retrieving sets of
contiguous sorted rows based on a predetermined and known location (the start
key
>> Solr does not provide a complex enough support to rank.
I believe Solr has a bunch of plug-ability to write your own custom ranking
approach. If you think you can't do your desired ranking with Solr, you're
probably wrong and need to ask for help from the Solr community.
>> retrieving data by
Mr Gupta,
Thanks so much for your reply!
In my use cases, retrieving data by keyword is one of them. I think Solr is
a proper choice.
However, Solr does not provide a complex enough support to rank. And,
frequent updating is also not suitable in Solr. So it is difficult to
retrieve data randomly
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
ne
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 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
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. A
10 matches
Mail list logo
