[
https://issues.apache.org/jira/browse/HBASE-13126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14340489#comment-14340489
]
Sean Busbey commented on HBASE-13126:
-------------------------------------
We reference HBaseTestingUtiltiy in our docs, most notably in the section where
we explain how downstream folks should test their HBase applications (ref [
Integration Testing with a HBase
Mini-Cluster|http://hbase.apache.org/book.html#_integration_testing_with_a_hbase_mini_cluster]).
So we should def not stop supporting it.
I agree we should change around where things live. the hbase-testing-util
module currently is just an aggregator. we could restructure to move these
things out of the src/test in hbase-server to there. What version could that be
in? Folks _should_ be using the hbase-testing-util as a dep, but might be
relying on the hbase-server test-jar instead. I guess 2.0.0?
> 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)
