[
https://issues.apache.org/jira/browse/HBASE-13126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14340689#comment-14340689
]
Enis Soztutar commented on HBASE-13126:
---------------------------------------
I think we should do the hadoop's model of exposing mini cluster to our
downstreamers. Hive/Phoenix, etc already have to depend on it for their own
testing, and we cannot just blindly ignore this. The reason we did not do this
before 1.0 is simply due to lack of time.
For 1.x we can at least annotate what is public, what is not public in HTU. HTU
itself is Public. I am expecting most of the {{start|stopMiniXXX()}} methods to
be Public as well, but things like {{createAndForceNodeToOpenedState()}} should
be Private.
> 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)
