[
https://issues.apache.org/jira/browse/HBASE-9203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13868757#comment-13868757
]
Liang Xie commented on HBASE-9203:
----------------------------------
to me, one main drawback of this design is the required padding mechanism, for
"index name" section inside index table's row key, maybe we can give a doc to
educate end-user, but other "indexed column(s) value(s)", are totally depend
on real user scenario, e.g. most of indexed column value probably very short,
say "a", and a few long value, say "abode...z", then even for the short "a"
value, based on current design, we still need to pad to sth like "a000..0", am
i correct? i don't have a better improvement idea through...
> 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 Design_Updated_2.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 was sent by Atlassian JIRA
(v6.1.5#6160)
