Re: 0.9.0.0 remaining jiras

I made a pass of those. KAFKA-2106 and KAFKA-1792 are related to improving the replica assignment. Since they likely involve a KIP discussion, it's probably too late to include them in 0.9.0.0. KAFKA-2434: This is on the old consumer. Any improvement that we do should probably be on the new consu

Re: 0.9.0.0 remaining jiras

Do we want to deprecate anything before 0.9.0 is released? Maybe the old producer? Ismael On Thu, Sep 17, 2015 at 8:07 PM, Dong Lin wrote: > Hey Jun, > > Should we also include https://issues.apache.org/jira/browse/KAFKA-2390 in > 0.9.0? Becket told me that this is one of those patches ( > http

Re: 0.9.0.0 remaining jiras

Hey Jun, Should we also include https://issues.apache.org/jira/browse/KAFKA-2390 in 0.9.0? Becket told me that this is one of those patches ( https://issues.apache.org/jira/browse/KAFKA-2387) needed for new consumer API. Thanks, Dong On Tue, Sep 15, 2015 at 11:01 PM, Jason Rosenberg wrote: > I

Re: 0.9.0.0 remaining jiras

I'd be interested to see: https://issues.apache.org/jira/browse/KAFKA-2434 (has patch available, we will be using 'old' consumer for some time) https://issues.apache.org/jira/browse/KAFKA-2125 (seems rather serious, unclear if no longer relevant with new code?) https://issues.apache.org/jira/bro

Re: 0.9.0.0 remaining jiras

Yep, It looks like this was only communicated originally to the dev list (and not the users list), so it wasn't obvious to all! Thanks, Jason On Mon, Sep 14, 2015 at 12:43 AM, Stevo Slavić wrote: > Hello Jason, > > Maybe this answers your question: > > http://mail-archives.apache.org/mod_mbox

Re: 0.9.0.0 remaining jiras

Is KAFKA-1811 worth considering for 0.9.0? Thanks! Eddie On Mon, Sep 14, 2015 at 4:34 PM, Jiangjie Qin wrote: > HI Jun, > > Can we also include KAFKA-2448 in 0.9 as well? We see this issue a few > times before and that cause replica fetcher th

Re: 0.9.0.0 remaining jiras

HI Jun, Can we also include KAFKA-2448 in 0.9 as well? We see this issue a few times before and that cause replica fetcher threads not startup. Thanks, Jiangjie (Becket) Qin On Sat, Sep 12, 2015 at 9:40 AM, Jun Rao wrote: > The following is a candidate list of jiras that we want to complete i

Re: 0.9.0.0 remaining jiras

Agree that these are very nice to have. We've seen many deployments that need to manage these on their own. However, if this is not ready before we are done adding security and the new consumer, it will make sense to still release 0.9.0 and add the broker management improvements in 0.9.1. I'm tryi

Re: 0.9.0.0 remaining jiras

We decided to rename 0.8.3 to 0.9.0 since it contains few large changes (Security, new consumer, quotas). On Sun, Sep 13, 2015 at 11:56 PM, Jason Rosenberg wrote: > Hi Jun, > > Can you clarify, will there not be a 0.8.3.0 (and instead we move straight > to 0.9.0.0)? > > Also, can you outline t

Re: 0.9.0.0 remaining jiras

Jun, Would be nice to have https://issues.apache.org/jira/browse/KAFKA-2106 (if not that, than related https://issues.apache.org/jira/browse/KAFKA-1792 ) in 0.9 release. Both have patch provided. If KAFKA-2106 is delivered, maybe KAFKA-1792 is redundant, not needed. For some reason KAFKA-2106 has

Re: 0.9.0.0 remaining jiras

Hello Jason, Maybe this answers your question: http://mail-archives.apache.org/mod_mbox/kafka-dev/201509.mbox/%3CCAFc58G-UScVKrSF1kdsowQ8Y96OAaZEdiZsk40G8fwf7iToFaw%40mail.gmail.com%3E Kind regards, Stevo Slavic. On Mon, Sep 14, 2015 at 8:56 AM, Jason Rosenberg wrote: > Hi Jun, > > Can you cl

Re: 0.9.0.0 remaining jiras

Hi Jun, Can you clarify, will there not be a 0.8.3.0 (and instead we move straight to 0.9.0.0)? Also, can you outline the man new features/updates for 0.9.0.0? Thanks, Jason On Sat, Sep 12, 2015 at 12:40 PM, Jun Rao wrote: > The following is a candidate list of jiras that we want to complete

Re: 0.9.0.0 remaining jiras

Excuse me, I'd put my issue in this list on the backburner, but resuming work on it this week. Cheers, Eddie Em 12/09/2015 13:40, "Jun Rao" escreveu: > The following is a candidate list of jiras that we want to complete in the > upcoming release (0.9.0.0). Our goal is to finish at least all the