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

Duo Zhang commented on HBASE-26157:
-----------------------------------

[~gjacoby] The PR is ready, where we exposed two methods, one is for getting a 
Region interface, the other is for getting an OnlineRegions interface. I think 
they could be used to verify the server side CP related things.

And on this problem
{quote}
Minor versions usually come out about annually, so we're giving client 
developers the choice between waiting up to a year, or using an IA.Private 
class that works right now but could break later. And for applications (or 
projects such as Phoenix) that need to support multiple versions of HBase, 
evolving interfaces in minor releases make compatibility really hard.
{quote}

The HBaseTestingUtility is still there, and you could still make use of it 
through the whole 3.x lifecycle. The only problem is you will get lots of 
warnings in your test code since it is deprecated. So here, we should try to 
improve the new TestingHBaseCluster interface, and once it is ready for most 
test code in Phoenix, the Phoenix could change to use it for most test code, 
and only leave a small set of UTs still rely on the internal new HBTU. Yes it 
could be changed during minor releases, but at that time when we want to change 
the shape, you could also join the discussion on how to better suit the Phoenix 
project.

Thanks.

> Expose some IA.LimitedPrivate interface in TestingHBaseCluster
> --------------------------------------------------------------
>
>                 Key: HBASE-26157
>                 URL: https://issues.apache.org/jira/browse/HBASE-26157
>             Project: HBase
>          Issue Type: Sub-task
>          Components: API, test
>            Reporter: Duo Zhang
>            Priority: Major
>
> For example, the coprocessor related interfaces such as Region, Store, etc.
> And for tags, since there is no way to get it at client side, we need to 
> expose some server side interfaces to allow users get them.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to