[
https://issues.apache.org/jira/browse/HBASE-23639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17044465#comment-17044465
]
Sean Busbey commented on HBASE-23639:
-------------------------------------
I have concerns making the chaos and cluster management stuff IA.Public. These
have historically been for our project's internal testing. Making them
IA.Public means now we have to consider the impact to them e.g. during upgrades.
[~mihir6692]and [~lokiore] would your concerns be addressed by making the
needed classes IA.LimitedPrivate? that would mean e.g. we wouldn't break them
on maintenance releases, but we might still break them on minor releases.
For {{HBaseClusterManager}} can y'all get more specific on what things are
needed for a downstream implementor of {{ClusterManager}}? I'd rather we
separate out those things instead of making the implementation by ssh something
we tell downstream folks we'll avoid breaking.
> Change InterfaceAudience for ClusterManager interface and HBaseClusterManager
> class public
> -------------------------------------------------------------------------------------------
>
> Key: HBASE-23639
> URL: https://issues.apache.org/jira/browse/HBASE-23639
> Project: HBase
> Issue Type: Improvement
> Components: API, integration tests, test
> Reporter: Mihir Monani
> Assignee: Lokesh Khurana
> Priority: Minor
> Attachments: HBASE-23639-master.patch
>
>
> In hbase-it package, Class like RESTApiClusterManager and HBaseClusterManager
> which has some part of implementation code for Chaos Action.
>
> If any user wants to create private implementation which resembles
> HBaseClusterManager, then it has to be merged with hbase-it package as
> ClusterManager Interface and it's extended implementations are private.
>
> We should make them public so anyone can have their own implementation and
> need to be merged with hbase-it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
