You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (Jira)" <ji...@apache.org> on 2021/06/01 05:40:00 UTC

[jira] [Commented] (HBASE-13126) Move HBaseTestingUtility and associated support classes into hbase-testing-utility module

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

Duo Zhang commented on HBASE-13126:
-----------------------------------

Plan to pick this up recently.

But in general, I do not think the original HBTU can be moved to hbase-testing-util, as we need to use it write UT for hbase-server module.

But we could introduce a new interface/class in hbase-testing-util module for end users and then mark HBTU and related classes as IA.Private.

If no big concerns, will start working with this direction.

Thanks.

> Move HBaseTestingUtility and associated support classes into hbase-testing-utility module
> -----------------------------------------------------------------------------------------
>
>                 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: 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)