I think we were just confirming whether that issue was fixed in 0.8.2 not.
Given that this issue only happens in unclean shutdown, I don't think it's
a blocker for 0.8.2. Also, the patch is not trivial and it's better to test
it out a bit longer in trunk.

Thanks,

Jun

On Thu, Jan 29, 2015 at 5:36 PM, Jiangjie Qin <j...@linkedin.com.invalid>
wrote:

> In meetup we said that KAFKA-1650 and follow up patches is included in
> 0.8.2, but it seems not on the list.
>
>
> On 1/29/15, 1:01 AM, "Magnus Edenhill" <mag...@edenhill.se> wrote:
>
> >+1 on librdkafka interop
> >
> >Minor nitpick:
> > KAFKA-1781 (state required gradle version in README)  is included in the
> >Release notes but is not actually fixed
> >
> >
> >2015-01-29 6:22 GMT+01:00 Jun Rao <j...@confluent.io>:
> >
> >> 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=223ac42a7a2a0
> >>dab378cc411f4938a9cea1eb7ea
> >> (commit 7130da90a9ee9e6fb4beb2a2a6ab05c06c9bfac4)
> >>
> >> /*******************************************
> >>
> >> Thanks,
> >>
> >> Jun
> >>
>
>

Reply via email to