Re: status of 0.8.2

wrt to KAFKA-1180 , I've uploaded a new version of the patch to the issue, refactored so that it can be applied and seems to work with 0.8.1.1 (and presumably trunk). It would be great if we could get this committed to trunk in some form, so that i

Re: status of 0.8.2

The new producer and the new offset management are already in trunk. The new consumer is to be developed. Thanks, Jun On Wed, Jul 9, 2014 at 1:54 PM, Kane Kane wrote: > Hello Jun, is new producer, consumer and offset management in the > trunk already? Can we start developing libraries with 0.

Re: status of 0.8.2

Hello Jun, is new producer, consumer and offset management in the trunk already? Can we start developing libraries with 0.8.2 support against trunk? Thanks! On Tue, Jul 8, 2014 at 9:32 PM, Jun Rao wrote: > Yes, 0.8.2 is compatible with 0.8.0 and 0.8.1 in terms of wire protocols > and the upgrade

Re: status of 0.8.2

Yes, 0.8.2 is compatible with 0.8.0 and 0.8.1 in terms of wire protocols and the upgrade can be done in place. Thanks, Jun On Tue, Jul 8, 2014 at 11:49 AM, Michal Michalski < michal.michal...@boxever.com> wrote: > One more question regarding 0.8.2 - is it planned to be a in-place, > no-downtim

Re: status of 0.8.2

Yup, that was my bad. I updated the comment to explain how the error is happening. /*** Joe Stein Founder, Principal Consultant Big Data Open Source Security LLC http://www.stealth.ly Twitter: @allthingshadoop *

Re: status of 0.8.2

One more question regarding 0.8.2 - is it planned to be a in-place, no-downtime release (I'm using 0.8.0 now)? By looking at the version number changes only I'd guess it is, but... ;-) Michal Kind regards, Michał Michalski, michal.michal...@boxever.com On 8 July 2014 18:22, Joel Koshy wrote:

Re: status of 0.8.2

Hi Joe, I had a question for you in that RB since I don't fully understand it. Maybe you can help clarify how the fix works. Thanks, Joel On Tue, Jul 08, 2014 at 10:55:56AM -0400, Joe Stein wrote: > I wrote it, so I can't commit it without other committers agreeing. > > Last I recall I updated

Re: status of 0.8.2

I think it should be ok that code as I recall is isolated. /*** Joe Stein Founder, Principal Consultant Big Data Open Source Security LLC http://www.stealth.ly Twitter: @allthingshadoop **

Re: status of 0.8.2

Thanks Joe, I'll let you know what I find. Do you anticipate any issues with it working in 0.8.1.1? Jason On Tue, Jul 8, 2014 at 10:55 AM, Joe Stein wrote: > 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 revi

Re: status of 0.8.2

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

Re: status of 0.8.2

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 wrote: > Two biggest features in 0.8.2 are Kafka-

Re: status of 0.8.2

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