Actually, the 0.8.0 beta1 release (from the latest 0.8 branch) depends on metrics 2.2.0. A couple of months ago, the 0.8 branch was using an unreleased version of metrics-core. When we heard that people have class conflicts with their existing metrics dependency, we downgraded on metrics-core in Kafka to the latest released version then.
Is metrics 3.0 officially released? If it's stable, we will upgrade to it in a future Kafka release. Thanks, Jun On Thu, Jun 27, 2013 at 5:53 AM, David Black <[email protected]>wrote: > So just to be clear, I'm referring to these jars in core/lib: > > metrics-annotation-3.0.0-c0c8be71.jar > metrics-core-3.0.0-c0c8be71.jar > > > On Thu, Jun 27, 2013 at 11:58 AM, David Black <[email protected] > >wrote: > > > Hi, > > > > W <[email protected]>e are looking at using Kafka, and currently > > experimenting with 0.8 > > > > We use Yammer Metrics 2.2.0 in our code base. The Kafka producer code > > currently has dependencies on a patched version of metrics which appears > to > > be a version somewhere between 2.2.0 and 3.0, which is not API compatible > > with metrics 2.2.0 . So this clashes with our 2.2.0 version of metrics. > > > > I have a couple of questions: > > > > 1. Why does the Producer code have a dependency on metrics? I can > > understand why metrics are useful for the broker, but it seems that > metrics > > could (at least) be optional for the producer. Are there any plans to > > change this? > > > > 2. Are there any plans to upgrade Kafka to the release of metrics 3.0 > > (where the root package name has been changed, and hence would not clash > > with our use of metrics 2.2)? > > > > thanks in advance > > > > David Black > > Workday > > > > >
