You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2016/06/07 17:41:21 UTC

[jira] [Comment Edited] (HBASE-15978) Netty API leaked into public API

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

Andrew Purtell edited comment on HBASE-15978 at 6/7/16 5:41 PM:
----------------------------------------------------------------

Related, we have some interfaces inheriting from Guava's Service, like the pluggable replication ones. This required a private patch to _HBase_ code when I normalized our Guava version cross stack internally.


was (Author: apurtell):
Related, we have some interfaces inheriting from Guava's Service, like the pluggable replication ones.

> 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
>            Priority: Critical
>
> 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)