[
https://issues.apache.org/jira/browse/HBASE-13126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14364090#comment-14364090
]
Sean Busbey commented on HBASE-13126:
-------------------------------------
I'd prefer to do it in 2.0, but in theory it should be doable for 1.1. It will
involve some classes changing which jar they live in, but that should only
result in an operational compatibility breakage (because people may have to
change how they launch their tests).
> 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)
