[
https://issues.apache.org/jira/browse/HBASE-26158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17392028#comment-17392028
]
Duo Zhang commented on HBASE-26158:
-----------------------------------
OK, here comes the question. Since you share a zk across Kafka, HBase, and a
custom process, then why it is the duty for HBase to provide the mini zk
cluster, not Kafka?
As I mentioned in the description, HBase is not designed to give end users the
ability to start a zk to write UT right? Curator-test is for this purpose, why
not just use curator-test?
Thanks.
> 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)
