Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sat, 11 Jun 2016 14:19:21 +0000 (UTC)
From: "Jurriaan Mous (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12976505.1465316439000.61833.1465654761147@Atlassian.JIRA>
In-Reply-To: <JIRA.12976505.1465316439000@Atlassian.JIRA>
References: <JIRA.12976505.1465316439000@Atlassian.JIRA> <JIRA.12976505.1465316439931@arcas>
Subject: [jira] [Updated] (HBASE-15978) Netty API leaked into public API
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sat, 11 Jun 2016 14:19:23 -0000


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

Jurriaan Mous updated HBASE-15978:
----------------------------------
    Attachment: HBASE-15978-guava.patch

> Netty API leaked into public API
> --------------------------------
>
>                 Key: HBASE-15978
>                 URL: https://issues.apache.org/jira/browse/HBASE-15978
>             Project: HBase
>          Issue Type: Bug
>          Components: Client
>    Affects Versions: 2.0.0
>            Reporter: Nick Dimiduk
>            Assignee: Jurriaan Mous
>            Priority: Blocker
>         Attachments: HBASE-15978-guava.patch, HBASE-15978.patch
>
>
> Noticed out public {{[client.Future|http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/Future.html]}} interface extends Netty, which means our public API is bound to a specific Netty API and release. IIRC we were minimizing our public-facing surface area and asserting ownership over the whole of it so as to control our compatibility. Ie, we've done this with Protobuf as well. Not sure if this has made it back to other branches.


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