Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Plain View
HBase >> mail # dev >> Re: [ANNOUNCE] Secondary Index in HBase - from Huawei


+
Andrew Purtell 2013-08-13, 18:31
+
Michael Segel 2013-08-14, 15:45
+
Vladimir Rodionov 2013-08-14, 16:40
+
Michael Segel 2013-08-14, 19:53
+
Andrew Purtell 2013-08-14, 20:52
+
Michael Segel 2013-08-14, 23:17
+
Vladimir Rodionov 2013-08-14, 21:04
+
Ted Yu 2013-08-14, 21:12
+
Michael Segel 2013-08-14, 23:19
+
James Taylor 2013-08-14, 21:18
+
lars hofhansl 2013-08-14, 22:35
+
Michael Segel 2013-08-14, 23:57
+
lars hofhansl 2013-08-15, 01:10
Copy link to this message
-
Re: [ANNOUNCE] Secondary Index in HBase - from Huawei
Are you sure? ;-)

We've had this discussion before.

On Aug 14, 2013, at 8:10 PM, lars hofhansl <[EMAIL PROTECTED]> wrote:

> No it doesn't in case 2 below. Quite the opposite.
>
> From: Michael Segel <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]; lars hofhansl <[EMAIL PROTECTED]>
> Sent: Wednesday, August 14, 2013 4:57 PM
> Subject: Re: [ANNOUNCE] Secondary Index in HBase - from Huawei
>
> Its not a question of their solution not working.
> Its that it takes a lot more resources on the read than the alternative.
>
>
> On Aug 14, 2013, at 5:35 PM, lars hofhansl <[EMAIL PROTECTED]> wrote:
>
> > Yep.
> >
> > 1. highly selective indexes + point gets -> global inverted index tables
> > 2. less selective indexes + queries returning many rows -> "local" indexes, such as the Huawei solution.
> >
> > Of course it's not quite that black and white. Global indexes that serve index covered queries (where the query can be answered from the index alone) would also work in many cases of non-selective queries.
> >
> > In the end it is quite simple (IMHO):
> > If a query retrieves data from only a single region, you want to able to hone into that region quickly, via a piece of global information.
> > If on the other hand a query returns data from many regions, you're better off handling the filtering locally.
> >
> > Just my $0.02.
> >
> > -- Lars
> >
> >
> > ________________________________
> > From: Andrew Purtell <[EMAIL PROTECTED]>
> > To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> > Sent: Wednesday, August 14, 2013 1:52 PM
> > Subject: Re: [ANNOUNCE] Secondary Index in HBase - from Huawei
> >
> >
> > On Wed, Aug 14, 2013 at 8:45 AM, Michael Segel <[EMAIL PROTECTED]>wrote:
> >
> >> This isn't too bad if you're doing a simple query against one index. You
> >> can do the work by RS and then join the results from all RS.
> >>
> >> However… what happens if you have two indexes and your result set is going
> >> to be the intersection of the indexes?
> >>
> >> Or you're going to do a join between two tables using the indexes to limit
> >> the result set?
> >>
> >> Now your design breaks down quickly.
> >>
> >
> > You may have just described their design assumptions.
> >
> > I'm not endorsing this per se, but suggesting it is not a good idea on
> > account it can't live up to the requirements of a pretty particular
> > strawman seems a step too far.
> >
> > Maybe someone from Huawei can talk a bit here about successful use cases?
> >
> >> You could also look at Lucene which we did a PoC a few years back.
> >
> > A certain large technology company has an HBase full text index built on
> > Lucene that might be offered as a contribution at some point. From what I
> > know of it, there are a different set of tradeoffs and it certainly won't
> > work for everyone, and not because the people working on it were not smart
> > enough to find a silver bullet.
> >
> > --
> > Best regards,
> >
> >    - Andy
> >
> > Problems worthy of attack prove their worth by hitting back. - Piet Hein
> > (via Tom White)
>
> The opinions expressed here are mine, while they may reflect a cognitive thought, that is purely accidental.
> Use at your own risk.
> Michael Segel
> michael_segel (AT) hotmail.com
>
>
>
>
>
>

The opinions expressed here are mine, while they may reflect a cognitive thought, that is purely accidental.
Use at your own risk.
Michael Segel
michael_segel (AT) hotmail.com

+
Anoop John 2013-08-13, 06:44
+
ramkrishna vasudevan 2013-08-13, 07:28
+
Nicolas Liochon 2013-08-13, 06:47
+
Jesse Yates 2013-08-13, 06:51
+
zhoushuaifeng 2013-08-18, 15:06
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB