Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 16 Jan 2014 02:26:20 +0000 (UTC)
From: "Sergey Shelukhin (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12685176.1387289784862.13664.1389839180139@arcas>
In-Reply-To: <JIRA.12685176.1387289784862@arcas>
References: <JIRA.12685176.1387289784862@arcas>
Subject: [jira] [Commented] (HBASE-10188) Deprecate ServerName constructors,
 but make it public.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Sergey Shelukhin commented on HBASE-10188:
------------------------------------------

I have no use case for this patch now, but I wonder as we get to higher cadence if the rule should be changed... people are just starting to upgrade from 94 and we already remove APIs.
Any change raises the ghosts of HBase shim in Hive, Pig, etc... Like Hadoop shim everyone is force to use.
I wonder if we should only remove when the requisite major release (in this case 94) is reasonably dead and support is dropped from places.

> Deprecate ServerName constructors, but make it public.
> ------------------------------------------------------
>
>                 Key: HBASE-10188
>                 URL: https://issues.apache.org/jira/browse/HBASE-10188
>             Project: HBase
>          Issue Type: Bug
>          Components: Client
>    Affects Versions: 0.96.1
>            Reporter: Nicolas Liochon
>            Assignee: Nicolas Liochon
>             Fix For: 0.96.2, 0.96.1.1
>
>         Attachments: 10188.v1.patch, hbase-10188.v2.patch
>
>
> It's in our public interface, we can't remove it that easily... See HBASE-10012?


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)