[
https://issues.apache.org/jira/browse/HBASE-10576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13919739#comment-13919739
]
James Taylor commented on HBASE-10576:
--------------------------------------
Thanks for isolating this piece [~rajesh23]. It's definitely useful to support
a local indexing feature in Phoenix. It's difficult for me to give you any
meaningful feedback until we starting going down the path of using it in the
context of Phoenix. One way we could approach this (and this is what Jesse did
with his secondary index work), would be to get the code into Phoenix first and
get it far enough along that it's clear it has everything required. Then, take
the code and propose moving it back into HBase. That way, you can get some good
usage and feedback along the way. As soon as we cut a 3.0 branch and a 4.0
branch (in a couple of days), we could get this into the master branch of
Phoenix and proceed down this path. If we go this route, it would probably be
best to do it first in a feature branch off of master.
Is that possible, or does the code required to live in HBase?
> Custom load balancer to co-locate the regions of two tables which are having
> same split keys
> --------------------------------------------------------------------------------------------
>
> Key: HBASE-10576
> URL: https://issues.apache.org/jira/browse/HBASE-10576
> Project: HBase
> Issue Type: Sub-task
> Components: Balancer
> Reporter: rajeshbabu
> Assignee: rajeshbabu
> Attachments: HBASE-10536_v2.patch, HBASE-10576.patch
>
>
> To support local indexing both user table and index table should have same
> split keys. This issue to provide custom balancer to colocate the regions of
> two tables which are having same split keys.
> This helps in Phoenix as well.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
