[
https://issues.apache.org/jira/browse/HBASE-9203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13741141#comment-13741141
]
rajeshbabu commented on HBASE-9203:
-----------------------------------
bq. What if some existing table(s) at customer site already uses the above
suffix ?
How about using metadata in HTableDescriptor for this purpose ?
In trunk we can add index tables to system namespaces,so we distinguish user
tables and index tables. In 94 its better to use metadata.
I will handle the above case and other comments in trunk patch.
For github raised an issue:
https://github.com/Huawei-Hadoop/hindex/issues/16
> 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
>
> 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
