hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rajesh babu Chintaguntla <chrajeshbab...@gmail.com>
Subject Re: Design review: Secondary index support through coprocess
Date Thu, 09 Jan 2014 15:59:53 GMT
Hi Sudarshan,

1-1 association between user regions and index regions maintained by using
custom load balancer(SecIndexLoadBalancer) which will always colocate user
region and corresponding index region on the same region server.
Let's suppose if we create an indexed table with split keys {a,b,c} then we
will create corresponding index table with same split keys.If a user region
with start key 'a' is assigned or assining to a region server RS, to assign
the index region with start key 'a', balancer gives the same RS as
destination and vice versa.

Thanks,
Rajeshbabu.

On Thursday, January 9, 2014, Sudarshan Kadambi (BLOOMBERG/ 731 LEXIN)
wrote:

> Could you explain how the 1-1 association between user and index table
> regions is maintained. I wasn't able to understand fully from the document.
>
> ----- Original Message -----
> From: Ted Yu <dev@hbase.apache.org <javascript:;>>
> To: dev@hbase.apache.org <javascript:;>
> At: Jan 8, 2014 3:41:40 PM
>
> Hi,
> Secondary index support is a frequently requested feature.
>
> Please find the updated design doc here:
>
> https://issues.apache.org/jira/secure/attachment/12621909/SecondaryIndex%20Design_Updated_2.pdf
>
> HBASE-9203 is the umbrella JIRA.
>
> Implementation patch was attached to HBASE-10222
>
> Thanks to Rajesh who works on this feature.
>
> Cheers
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message