I wrote it, so I can't commit it without other committers agreeing.

Last I recall I updated the patch from the feedback in the reviewboard but
haven't looked at it in months.

I am glad though it resolved the issue you were having and we can figure
how to get the patch to work with 0.8.1.1 if you run into problems.

/*******************************************
 Joe Stein
 Founder, Principal Consultant
 Big Data Open Source Security LLC
 http://www.stealth.ly
 Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
********************************************/


On Tue, Jul 8, 2014 at 10:45 AM, Jason Rosenberg <j...@squareup.com> wrote:

> Is there a blocker to getting the patch for kafka-1180 applied?  Is the
> patch for 0.8.0 no longer compatible for trunk?  I'm actually going to see
> if I can get it to work for 0.8.1.1 today.
>
> Thanks,
>
> Jason
>
>
> On Mon, Jul 7, 2014 at 9:41 PM, Jun Rao <jun...@gmail.com> wrote:
>
> > Two biggest features in 0.8.2 are Kafka-based offset management and the
> new
> > producer. We are in the final stage of testing them. We also haven't
> fully
> > tested the delete topic feature. So, we are probably 4-6 weeks away from
> > releasing 0.8.2.
> >
> > For kafka-1180, the patch hasn't been applied yet and we will need a
> patch
> > for trunk.
> >
> > Thanks,
> >
> > Jun
> >
> >
> > On Mon, Jul 7, 2014 at 7:31 AM, Jason Rosenberg <j...@squareup.com>
> wrote:
> >
> > > What's the status for an 0.8.2 release?  We are currently using 0.8.0,
> > and
> > > would like to upgrade to take advantage of some of the per-topic
> > retention
> > > options available now in 0.8.1.
> > >
> > > However, we'd also like to take advantage of some fixes coming in 0.8.2
> > > (e.g. deleting topics).
> > >
> > > Also, we have been using a patch for (
> > > https://issues.apache.org/jira/browse/KAFKA-1180) applied to 0.8.0.
> >  This
> > > is marked as scheduled for 0.8.2, with a patch available, but I'm not
> > sure
> > > if this has been committed and applied to the 0.8.2 branch yet.
> > >
> > > Thanks,
> > >
> > > Jason
> > >
> >
>

Reply via email to