[jira] [Updated] (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 updated HBASE-26081: -- Description: 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=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17358108 > 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=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17358108 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (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 updated HBASE-26081: -- Description: 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=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. was: 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=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17358108 > 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=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)
[jira] [Updated] (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 updated HBASE-26081:
--
Hadoop Flags: Incompatible change,Reviewed
Release Note:
Copy HBaseCommonTestingUtility, HBaseZKTestingUtility, HBaseTestingUtility,
HBaseCluster, MiniHBaseCluster, StartMiniClusterOption to hbase-testing-util,
and mark them as Deprecated. They will be removed in 4.0.0. End users should
use TestingHBaseCluster for writing UTs in the future.
And in hbase-server and related modules, these classes are renamed.
HBaseCommonTestingUtility -> HBaseCommonTestingUtil
HBaseZKTestingUtility -> HBaseZKTestingUtil
HBaseTestingUtility -> HBaseTestingUtil
HBaseCluster -> HBaseClusterInterface
MiniHBaseCluster -> SingleProcessHBaseCluster
StartMiniClusterOption -> StartTestingClusterOption
And all these classes are marked as IA.LimitedPrivate("Phoenix"), and
IS.Evolving. Except Phoenix, other end users should not use them any more.
> 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
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (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 updated HBASE-26081: -- Summary: Copy HBTU to hbase-testing-util, rename the HBTU related classes in hbase-server and mark them as IA.LimitedPrivate (was: Copy HBTU to hbase-testing-util, rename the HBTU related classes in hbase-server and mark them as IA.Private) > 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 >Priority: Major > Fix For: 3.0.0-alpha-2 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
