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/07/19 10:05:00 UTC
[jira] [Reopened] (HBASE-26081) Copy HBTU to hbase-testing-util,
rename the HBTU related classes in hbase-server and mark them as
IA.LimitedPrivate
[ https://issues.apache.org/jira/browse/HBASE-26081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Duo Zhang reopened HBASE-26081:
-------------------------------
> Copy HBTU to hbase-testing-util, rename the HBTU related classes in hbase-server and mark them as IA.LimitedPrivate
> -------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-26081
> URL: https://issues.apache.org/jira/browse/HBASE-26081
> Project: HBase
> Issue Type: Sub-task
> Components: API, test
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 3.0.0-alpha-2
>
>
> See the discussions in the parent issue on why we want to do this.
> This is the final decision:
> https://issues.apache.org/jira/browse/HBASE-13126?focusedCommentId=17358108&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17358108
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)