[
https://issues.apache.org/jira/browse/HBASE-13126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17358108#comment-17358108
]
Duo Zhang commented on HBASE-13126:
-----------------------------------
Maybe a possible way is that, we mark HBTU as deprecated and introduce another
class for end users to use. And on the next major release, we just introduce a
another class in hbase-server for our internal usage, and copy the whole HBTU
related classes to hbase-testing-util module, and keep them there for a whole
major release, and then we remove them when the next major release is out. So
end users will have plenty of time to change their code.
> Provide alternate mini cluster classes other than HBTU for downstream users
> to write unit tests
> -----------------------------------------------------------------------------------------------
>
> Key: HBASE-13126
> URL: https://issues.apache.org/jira/browse/HBASE-13126
> Project: HBase
> Issue Type: Umbrella
> Components: API
> Affects Versions: 2.0.0
> Reporter: Sean Busbey
> Priority: Critical
> Fix For: 3.0.0-alpha-2
>
>
> 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
(v8.3.4#803005)
