[
https://issues.apache.org/jira/browse/KAFKA-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13622458#comment-13622458
]
Jun Rao commented on KAFKA-826:
-------------------------------
I pinged Coda and the following are the answers that I got.
1. How stable is 3.0.0-Beta1?
The code is actually less complicated than Metrics 2 and far better tested: no
thread pools, no lifecycles, no static references, just simple objects.
2. Is it true that 3.0.0-Beta1 has no classpath conflict with 2.x? In other
words, can an application use both jars in the same JVM?
Many of the classes have changed names and/or packages, but I didn't intend for
there to be no classpath conflicts. You might be able to get away with it, but
someone somewhere will step on something sharp, I'm sure.
3. Will there be any api change btw 3.0.0-Beta1 and the final 3.0 release?
Probably, yes.
4. Were there any api changes btw 3.0.0-Beta1 and 3.0.0-SNAPSHOT (the one that
we are currently using in Kafka 0.8)?
I don't know which snapshot build you're using, but I would imagine there are a
lot of changes.
Based on the above, my feeling is that Kafka 0.8 release should use metrics 2.x
since (1) it has been stable; (2) people who depend on 2.x have no risk in
using Kafka 0.8; (3) the api of 3.x is likely going to change again. In a post
0.8 release, we can upgrade to metrics 3.x when the final version is released
and is deemed stable. Any concern with this approach?
> Make Kafka 0.8 depend on metrics 2.2.0 instead of 3.x
> -----------------------------------------------------
>
> Key: KAFKA-826
> URL: https://issues.apache.org/jira/browse/KAFKA-826
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8
> Reporter: Neha Narkhede
> Assignee: Dragos Manolescu
> Priority: Blocker
> Labels: build, kafka-0.8, metrics
> Attachments: kafka-fix-for-826.patch, kafka-fix-for-826-take2.patch
>
>
> In order to mavenize Kafka 0.8, we have to depend on metrics 2.2.0 since
> metrics 3.x is a huge change as well as not an officially supported release.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
