[
https://issues.apache.org/jira/browse/KUDU-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16441705#comment-16441705
]
Todd Lipcon commented on KUDU-2411:
-----------------------------------
I think exposing BaseKuduTest as a public artifact would be pretty messy.
Having a public API as a base class full of implementation leaves us really
exposed.
Exposing a MiniKuduCluster and various utilities that use it makes more sense,
and seems more easy to produce a stable API.
One idea to solve the binary dependence would be to build some kind of
stripped-down minicluster docker image. Given that all major platforms support
docker it's probably the easiest way to distribute a minicluster that can run
on dev machines running osx or windows. Of course we'd want to preserve the
existing "bin-dir" type argument, but having an alternative that uses "docker
run apachekudu:mini-cluster" or somesuch seems pretty nice.
> Create a public test utility artifact
> -------------------------------------
>
> Key: KUDU-2411
> URL: https://issues.apache.org/jira/browse/KUDU-2411
> Project: Kudu
> Issue Type: Improvement
> Components: java
> Affects Versions: 1.7.0
> Reporter: Grant Henke
> Assignee: Grant Henke
> Priority: Major
>
> Create a public published test utility jar that contains useful testing
> utilities for applications that integrate with Kudu including things like
> BaseKuduTest.java and MiniKuduCluster.java.
> This has the added benefit of eliminating the unusual dependency on all of
> kudu-clients test in each of the other java modules. This could likely be
> used in our examples code too.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
