[
https://issues.apache.org/jira/browse/KAFKA-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13622469#comment-13622469
]
Dragos Manolescu commented on KAFKA-826:
----------------------------------------
Thank you Jun for the analysis! From my perspective the approach you suggested
is sound. FWIW a couple of weeks ago I "ported" the Kafka code to the latest
(at the time) metrics 3.0.0 APIs. The code compiled and tests passed, but I
don't know the extent that demonstrates that the instrumentation and reporting
worked as it should. I'm bringing it up because I feel that once 3.0.0 is
released the port is mechanical.
> 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
