hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gaurav Menghani (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12650) Move ServerName to hbase-common
Date Sat, 06 Dec 2014 15:37:12 GMT

    [ https://issues.apache.org/jira/browse/HBASE-12650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14236853#comment-14236853
] 

Gaurav Menghani commented on HBASE-12650:
-----------------------------------------

Is there is a branch for 2.0.0 (where hydrabase will land, I presume)? If yes, that's what
I meant. Otherwise, I will just land it on trunk and the hydrabase feature branch.

> Move ServerName to hbase-common
> -------------------------------
>
>                 Key: HBASE-12650
>                 URL: https://issues.apache.org/jira/browse/HBASE-12650
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 2.0.0
>            Reporter: Gaurav Menghani
>            Assignee: Gaurav Menghani
>            Priority: Blocker
>             Fix For: 2.0.0
>
>
> The idea is to move ServerName to hbase-common, so that other modules like hbase-consensus
which (would) depend on ServerName, but can't depend on hbase-client, since hbase-client would
depend on them. Moreover, it looks logical that ServerName not be a part of the client module.
It is a shared class between multiple modules, so it should be in hbase-common.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message