You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Thiruvel Thirumoolan (JIRA)" <ji...@apache.org> on 2016/12/02 22:27:58 UTC
[jira] [Created] (HBASE-17244) Refactor StartcodeAgnosticServerName
so it doesn't extend ServerName
Thiruvel Thirumoolan created HBASE-17244:
--------------------------------------------
Summary: Refactor StartcodeAgnosticServerName so it doesn't extend ServerName
Key: HBASE-17244
URL: https://issues.apache.org/jira/browse/HBASE-17244
Project: HBase
Issue Type: Sub-task
Reporter: Thiruvel Thirumoolan
Assignee: Thiruvel Thirumoolan
Priority: Minor
Follow up jira to address [~toffer]'s review comments @ https://reviews.apache.org/r/53242/. /cc [~devaraj].
{quote}
Apart from sharing a lot of functionality as ServerName it seems there is no need to be a subclass. In fact it is prolly not good design to do so as it may cause unwanted mixups for the user. (ie both instances in the same collection). Since this is functionally correct. We can address this in a separate jira. Prolly something we should do before we pull in the next jira.
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)