hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9203) Secondary index support through coprocessors
Date Mon, 19 Aug 2013 18:34:52 GMT

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

Ted Yu commented on HBASE-9203:

bq. When the index is on more than one column we need to take values of all the columns and
add them in the rowkey in the same order of columns added to the index specifier.
What if user specifies two indices on the same set of columns but in different order ?

bq. This index name max length is configurable using the parameter <<>>.
Was there a typo above (w.r.t. the parameter name) ?
If the max length is changed after index table is created and written to, would index row
key parsing be affected ?

bq. For this we take the maxValueLength for an indexed column when table is created.
What if the maxValueLength cannot cover the actual value for indexed column from the user
query ?

bq. In order to make integers compare correctly, we need to flip the sign bit.

OrderedBytes is in 0.95 and trunk. It should help with this use case.
> 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

View raw message