[jira] [Commented] (HBASE-26158) MiniZooKeeperCluster should not be IA.Public

["Geoffrey Jacoby (Jira)" <ji...@apache.org>]

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

Geoffrey Jacoby commented on HBASE-26158:
-----------------------------------------

[~zhangduo] - I'm not sure that this is a correct assumption. 

For example, my colleague [~bharathv] recently wrote an IT test that used the MiniZooKeeperCluster to share a ZK quorum between an in-memory Kafka instance, an HBase minicluster, and a custom process implementing the HBase RegionServer API. (It's part of a project that will be contributed to Phoenix when it's closer to final form.)  

And I can see other valid test cases for using the MiniZooKeeperCluster, such as verifying that a custom coproc or replication endpoint (particularly the endpoint) don't leak resources or do other bad things if ZK connectivity is lost. 

> MiniZooKeeperCluster should not be IA.Public
> --------------------------------------------
>
>                 Key: HBASE-26158
>                 URL: https://issues.apache.org/jira/browse/HBASE-26158
>             Project: HBase
>          Issue Type: Sub-task
>          Components: API, test
>            Reporter: Duo Zhang
>            Priority: Major
>
> End users do not need to test HBase when zookeeper is broken. And if users want to start only a zookeeper cluster, they can just use curator-test, so I do not think we should expose this class as IA.Public.



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