[
https://issues.apache.org/jira/browse/HBASE-15978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319040#comment-15319040
]
Keith Turner commented on HBASE-15978:
--------------------------------------
I have a change in a branch for APIlyzer that I have never merged in. This
change allows APILyzer to use annotations to define the API, like HBase and
Hadoop do. I need to finish that patch for apilyzer up and get it in. To test
the patch I was using HBase or Hadoop, I can remember. I was able to do checks
like ensure that Public+Stable annotated types only reference other
Public+Stable annotated types. Doing this I found cases where Public+Stable
types referenced Public+Evolving types. I'll try to get that merged in and
another version of apilyzer released.
> 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: Blocker
>
> 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)
