hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anoop Sam John (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9203) Secondary index support through coprocessors
Date Tue, 12 May 2015 12:14:03 GMT

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

Anoop Sam John commented on HBASE-9203:

As discussed above and in mail list, it is not possible for a global solution which satisfy
all sort of needs.  So to HBase core code we might not add any indexing.  As you said, Phoenix
have local indexing solution. It also has global indexing solution.  Depending on the need
and data size user can opt for any.  The local indexing try to reduce the write time hit and
make things 100% strong consistent model.  

bq.But hey! What do I know. I'm not a committer ... ;-P
One idea or comment is treated as per the quality of it and not based on whether it is from
committer or not. I have not come across some non committers complaining that their comments/ideas
are just ignored.  Just saying.

> Secondary index support through coprocessors
> --------------------------------------------
>                 Key: HBASE-9203
>                 URL: https://issues.apache.org/jira/browse/HBASE-9203
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: rajeshbabu
>            Assignee: rajeshbabu
>         Attachments: SecondaryIndex Design.pdf, SecondaryIndex Design_Updated.pdf, SecondaryIndex
> 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 was sent by Atlassian JIRA

View raw message