kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Carey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-826) Make Kafka 0.8 depend on metrics 2.2.0 instead of 3.x
Date Wed, 03 Apr 2013 22:19:17 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13621416#comment-13621416

Scott Carey commented on KAFKA-826:

My main complaint prior to this was two-fold:

* Early versions of metrics 3.x had classpath collisions with 2.2.x , so we would be unable
to have both in the same application and we already use 2.2.
* There was no official version of metrics 3.x published anywhere to consume, no roadmap,
and the developer was MIA for months.  Kafka would have had to publish their own artifact
version which gets messy fast and would have likely api compatibility issues with any future
final metrics 3.0.x release and therefore be very difficult to use kafka 0.8 and the final
metrics 3.0 in the same application.

If 3.x is stable enough API wise, I'd be fine with keeping kafka on it.   I believe 3.x no
longer collides with 2.2.x in a classpath, but have not tested that recently, meaning we could
migrate to 3.x at our own pace and not have to time it to be in sync with use of Kafka 0.8.
> 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

View raw message