hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thiruvel Thirumoolan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-17244) Refactor StartcodeAgnosticServerName so it doesn't extend ServerName
Date Mon, 06 Feb 2017 21:32:42 GMT

     [ https://issues.apache.org/jira/browse/HBASE-17244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Thiruvel Thirumoolan updated HBASE-17244:
    Component/s: FavoredNodes

> 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
>          Components: FavoredNodes
>            Reporter: Thiruvel Thirumoolan
>            Assignee: Thiruvel Thirumoolan
>            Priority: Minor
>             Fix For: 2.0.0
> 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

View raw message