Re: [VOTE] 0.8.2.0 Candidate 3

[Jun Rao <ju...@confluent.io>]

Hi, Alex,

Thanks for testing RC3.

Broker.connectionString() is actually not part of the public api for the
producer. Is there a particular reason that you need to use this api?

Thanks,

Jun

On Sat, Jan 31, 2015 at 1:53 PM, Alex The Rocker <al...@gmail.com>
wrote:

> Hello,
>
> I have read Broker.scala source code, and I found the answer:
>  - With Kafka 0.8.1.1 we used Broker.getConnectionString() in our Java
> code.
>  - With Kafka 0.8.2.0, this method has been replaced by a 0-arity method
> without the "get" prefix, so we have to change our Java code to call
> Broker.connectionString()
>
> So despite binary compatibility is broken, we have a by-pass.
> I hope this will help other people relying on this API...
>
> and I'm going to continue tests with 0.8.2 rc3..
>
> Alex
>
> 2015-01-31 21:23 GMT+01:00 Alex The Rocker <al...@gmail.com>:
>
> > Hello,
> >
> > I ran my own tests made with kafka_2.10-0.8.1.1.tgz binaries with our
> > application:
> >
> > 1st test:
> > ======
> >   replace all kafka .jar files in our application on consumming side
> >   (without recompiling anything)
> >   => tests passed, OK
> >
> > 2nd test:
> > =======
> >   replace all kafka .jar files in our application on producubg side
> >   (without recompiling anything)
> >   => KO, we get this error:
> >
> > 2015-01-31 20:54:00,094 [Timer-2] ERROR c.d.i.t.StdOutErrRedirect -
> > Exception in thread "Timer-2"
> > 2015-01-31 20:54:00,111 [Timer-2] ERROR c.d.i.t.StdOutErrRedirect -
> > java.lang.NoSuchMethodError:
> > kafka.cluster.Broker.getConnectionString()Ljava/lang/String;
> >
> > Which means that binary compatibility with 0.8.1.1 version has been
> broken.
> > We use getConnectionString() to get Broker's zookeepers adresses, see
> this
> > answer from Neha:
> >
> >
> >
> http://mail-archives.apache.org/mod_mbox/kafka-users/201404.mbox/%3CCAOG_4QYnWrB=TmRTCRyF8-PdAgY_CGFe_cxoTQBCLrKj2+XmwA@mail.gmail.com%3E
> >
> > If the kafka.cluster.Broker.getConnectionString() method has been removed
> > with Kafka 0.8.2.0, then what is the suitable replacement for it ?
> >
> > Thanks
> > Alex
> >
> >
> >> -----Original Message-----
> >> From: Jun Rao [mailto:jun@confluent.io]
> >> Sent: Thursday, January 29, 2015 6:22
> >> To: dev@kafka.apache.org; users@kafka.apache.org;
> >> kafka-clients@googlegroups.com
> >> Subject: [VOTE] 0.8.2.0 Candidate 3
> >>
> >> This is the third candidate for release of Apache Kafka 0.8.2.0.
> >>
> >> Release Notes for the 0.8.2.0 release
> >>
> >>
> https://people.apache.org/~junrao/kafka-0.8.2.0-candidate3/RELEASE_NOTES.html
> >>
> >> *** Please download, test and vote by Saturday, Jan 31, 11:30pm PT
> >>
> >> Kafka's KEYS file containing PGP keys we use to sign the release:
> >> http://kafka.apache.org/KEYS in addition to the md5, sha1 and sha2
> >> (SHA256) checksum.
> >>
> >> * Release artifacts to be voted upon (source and binary):
> >> https://people.apache.org/~junrao/kafka-0.8.2.0-candidate3/
> >>
> >> * Maven artifacts to be voted upon prior to release:
> >> https://repository.apache.org/content/groups/staging/
> >>
> >> * scala-doc
> >> https://people.apache.org/~junrao/kafka-0.8.2.0-candidate3/scaladoc/
> >>
> >> * java-doc
> >> https://people.apache.org/~junrao/kafka-0.8.2.0-candidate3/javadoc/
> >>
> >> * The tag to be voted upon (off the 0.8.2 branch) is the 0.8.2.0 tag
> >>
> https://git-wip-us.apache.org/repos/asf?p=kafka.git;a=tag;h=223ac42a7a2a0dab378cc411f4938a9cea1eb7ea
> >> (commit 7130da90a9ee9e6fb4beb2a2a6ab05c06c9bfac4)
> >>
> >> /*******************************************
> >>
> >> Thanks,
> >>
> >> Jun
> >>
> >
> >
>