[ 
https://issues.apache.org/jira/browse/HBASE-9203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13744051#comment-13744051
 ] 

Ted Yu commented on HBASE-9203:
-------------------------------

bq. We will hide the index table regions from this actual load balancer.
The actual load balancer would support favored nodes feature. We should 
consider the placement not just for one replica of HFiles but the second and 
third replica as well.

bq. The index table can be created with a name which is the actual table name 
suffixed with a predefined pattern ‘_idx’.
Using fixed table name suffix is not flexible.

For CreateTableWithSplits diagram, the flow is different from that of 
TableCreate diagram - there is second createTable call issued by Master. What 
if this second call has some IOException ? Would the user table be dropped in 
that case ?

bq. When the user table is having N number of indices, N entries need to get 
added into the index region for this user table row.

The above implementation may result in the size of index table region being 
larger than the size of user table region. I assume split policy would be 
customized for index table.
                
> Secondary index support through coprocessors
> --------------------------------------------
>
>                 Key: HBASE-9203
>                 URL: https://issues.apache.org/jira/browse/HBASE-9203
>             Project: HBase
>          Issue Type: New Feature
>    Affects Versions: 0.98.0
>            Reporter: rajeshbabu
>            Assignee: rajeshbabu
>         Attachments: SecondaryIndex Design.pdf
>
>
> We have been working on implementing secondary index in HBase and open 
> sourced  on hbase 0.94.8 version.
> The project is available on github.
> https://github.com/Huawei-Hadoop/hindex
> This Jira is to support secondary index on trunk(0.98).
> Following features will be supported.
> -          multiple indexes on table,
> -          multi column index,
> -          index based on part of a column value,
> -          equals and range condition scans using index, and
> -          bulk loading data to indexed table (Indexing done with bulk load)
> Most of the kernel changes needed for secondary index is available in trunk. 
> Very minimal changes needed for it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to