[
https://issues.apache.org/jira/browse/KAFKA-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14730307#comment-14730307
]
Ewen Cheslack-Postava commented on KAFKA-2516:
----------------------------------------------
Compatibility czar checking in. Technically we've already released
ProducerPerformance under o.a.k.clients.tools. Normally I'd say we need to take
care to maintain some compatibility, but I think for this particular tool we
can safely just move it. I doubt many people have that tool running in an
automated way via the class name rather than the wrapper script, and in such a
way that it would actually seriously break anything for them.
However, I wanted to bring it up because we don't have an official policy
around this and we've recently tried to be more careful about tools
compatibility since they are a public API. Clearly the argument here is that
some tools are not created equal and deciding as a project that benchmarking
and simple testing tools are a separate class from normal operational tools and
that we're not going to make compatibility guarantees for them. (If we're going
that route, we could annotate them permanently with Unstable.) Also, this
underscores the importance of getting the tools into the right location before
they are released for the first time!
> Rename o.a.k.client.tools to o.a.k.tools
> ----------------------------------------
>
> Key: KAFKA-2516
> URL: https://issues.apache.org/jira/browse/KAFKA-2516
> Project: Kafka
> Issue Type: Bug
> Reporter: Gwen Shapira
> Priority: Blocker
> Fix For: 0.8.3
>
>
> Currently our new performance tools are in o.a.k.client.tools but packaged in
> kafka-tools not kafka-clients. This is a bit confusing.
> Since they deserve their own jar (you don't want our client tools packaged in
> your app), lets give them a separate package and call it o.a.k.tools.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
