[
https://issues.apache.org/jira/browse/HBASE-26157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17391770#comment-17391770
]
Geoffrey Jacoby commented on HBASE-26157:
-----------------------------------------
Thanks, [~zhangduo] I'm very interested in seeing what this proposal looks
like. My concern is:
What if we miss some needed method on the interface, and we don't realize it
until after HBase 3.0 is released? Am I correct that because of semver the
soonest a fix to the interface could be released would be HBase 3.1, and that
the fix could not be backported to 3.0.x?
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.
> 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)
