[
https://issues.apache.org/jira/browse/HBASE-18860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201106#comment-16201106
]
Zach York commented on HBASE-18860:
-----------------------------------
[~stack] The most intrusive patch in terms of internals is HBASE-18775. The
other stuff can be in a separate module, but I don't know if there will be
enough code to justify that.
I'm also struggling with naming. I was going to create a package under o.a.h.h
in hbase-server, but couldn't think of the proper naming structure
(o.a.h.h.readreplicaclusters seems way too verbose). Do you have any ideas? I
think the naming would be easily carried through for either the module or
package.
> Determine where to move ReadReplicaClustersTableNameUtils
> ---------------------------------------------------------
>
> Key: HBASE-18860
> URL: https://issues.apache.org/jira/browse/HBASE-18860
> Project: HBase
> Issue Type: Sub-task
> Affects Versions: HBASE-18477
> Reporter: Zach York
> Assignee: Zach York
> Priority: Minor
>
> In HBASE-18773, Stack brought up the (good) point that
> ReadReplicaClustersTableNameUtils does not really belong in the hbase-common
> package. This follow-up JIRA is to determine the correct place for
> Read-Replica code and to move this utils class there.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)