[
https://issues.apache.org/jira/browse/HBASE-6087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286123#comment-13286123
]
Jesse Yates commented on HBASE-6087:
------------------------------------
{quote}
Why cannot we use HConstants.HBCK_CODE_SERVERNAME ?
{quote}
I'm moved it down because would then need to bring along ServerName, which then
brings along org.apache.hadoop.hbase.protobuf.ProtobufUtil and
org.apache.hadoop.hbase.protobuf.generated.ZooKeeperProtos.RootRegionServer,
which seemed kind of excessive. And for modularization and breaking the
HConstants anti-pattern, it makes more sense to just move it into
AssignmentManager (the only place that actually references that value).
> Add hbase-common module
> -----------------------
>
> Key: HBASE-6087
> URL: https://issues.apache.org/jira/browse/HBASE-6087
> Project: HBase
> Issue Type: Bug
> Components: build
> Affects Versions: 0.96.0
> Reporter: Jesse Yates
> Assignee: Jesse Yates
> Attachments: hbase-6087-v0.patch, hbase-6087-v1.patch
>
>
> Add an hbase-common module so common/utility classes can be pulled up out of
> hbase-server. This is _not_ the moving of classes, just the general project
> setup.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
