You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Mikhail Antonov (JIRA)" <ji...@apache.org> on 2015/03/16 23:14:39 UTC

[jira] [Commented] (HBASE-13126) Clean up API for unintended methods within non-private classes.

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

Mikhail Antonov commented on HBASE-13126:
-----------------------------------------

So looking at the label, this isn't scoped for 1.1 as of now, or is it? Is it being worked on by someone? Thinking if it makes sense to split in 2 - one for 1.1 annotations, one for 2.0 - move?

> Clean up API for unintended methods within non-private classes.
> ---------------------------------------------------------------
>
>                 Key: HBASE-13126
>                 URL: https://issues.apache.org/jira/browse/HBASE-13126
>             Project: HBase
>          Issue Type: Task
>          Components: API
>    Affects Versions: 2.0.0
>            Reporter: Sean Busbey
>            Priority: Blocker
>             Fix For: 2.0.0
>
>
> Over in the review for HBASE-12972, [~enis] mentioned that one of the HBTU methods wasn't intended for public consumption.
> Can we build a list of such methods across the API, appropriately annotate them for 2.0, and deprecate them in earlier versions with a warning that they're going to be restricted?



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