[
https://issues.apache.org/jira/browse/HBASE-26158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17392574#comment-17392574
]
Geoffrey Jacoby commented on HBASE-26158:
-----------------------------------------
As for why I think it's not good to have one ZK API for internal use cases and
another for end-users:
HBase isn't just a fast, powerful key-value storage engine. It's also a
platform (and platform component) on which other developers build applications.
One of the principles of platform development is that when an internal use case
and an external use case are both trying to do the same thing, they should
always use the same API [1]. This allows platform developers (such as the HBase
community) to experience the ease or difficulties that end-users experience
when using their platform.
[1] https://deviq.com/practices/dogfooding
> 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)
