Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Fri, 2 Dec 2016 22:27:58 +0000 (UTC)
From: "Thiruvel Thirumoolan (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.13025230.1480717641000.428048.1480717678569@Atlassian.JIRA>
In-Reply-To: <JIRA.13025230.1480717641000@Atlassian.JIRA>
References: <JIRA.13025230.1480717641000@Atlassian.JIRA> <JIRA.13025230.1480717641516@arcas>
Subject: [jira] [Created] (HBASE-17244) Refactor StartcodeAgnosticServerName
 so it doesn't extend ServerName
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 02 Dec 2016 22:28:00 -0000

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)