[
https://issues.apache.org/jira/browse/HBASE-9203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13744672#comment-13744672
]
ramkrishna.s.vasudevan commented on HBASE-9203:
-----------------------------------------------
>>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.
Okie. So the HFiles of main and index table should be placed on the same node.
>>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.
Currently there is no customization here. Mostly it will be the same data but
the thing is we would read the HFile twice to create the top and bottom files
for the index region.
Your concern seems valid, need to check those instances.
>>Using fixed table name suffix is not flexible.
Yes - I think we can mitigate this (with namespaces in place now).
>>here is second createTable call issued by Master. What if this second call
>>has some IOException ?
overall there is some lack of mechanism to know what happens on the CP calls.
Most of the master operations are now happening on the RPC handler thread
rather than the main threadmainly to reduce the impact of this problem.
> 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
