You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by Neha Narkhede <ne...@gmail.com> on 2012/06/15 21:41:52 UTC

Replication status

Hi,

As of this week, we closed:

KAFKA-335: Embedded controller
KAFKA-341: Create a new single host system test to validate all
replicas on 0.8 branch

We have people signed up on the following jiras:

KAFKA-329: Create topic support (revisit based on v3 design)
KAFKA-339: Use multi-fetch for follower replication
KAFKA-350: Improve the highwatermark maintenance to handle failures
KAFKA-353: Tie Producer-side ack with high watermark and progress of replicas

The following jiras can be worked on in parallel and we welcome
contribution from the community.

KAFKA-288: rework java producer API
KAFKA-289: reuse TopicData when sending produce request
KAFKA-354: refactor setter/getter in scala style
KAFKA-355: Move the highwatermark maintenance logic out of Log.
KAFKA-356: create a generic thread class

Thanks,
Neha

Re: Replication status

Posted by Neha Narkhede <ne...@gmail.com>.

Sounds great !

Thanks,
Neha

On Fri, Jun 15, 2012 at 2:08 PM, Joe Stein <cr...@gmail.com> wrote:
> I can start working on
>
> KAFKA-354: refactor setter/getter in scala style
>
> I will assign the JIRA to myself later tonight/tomorrow
>
> On Fri, Jun 15, 2012 at 3:41 PM, Neha Narkhede <ne...@gmail.com>wrote:
>
>> Hi,
>>
>> As of this week, we closed:
>>
>> KAFKA-335: Embedded controller
>> KAFKA-341: Create a new single host system test to validate all
>> replicas on 0.8 branch
>>
>> We have people signed up on the following jiras:
>>
>> KAFKA-329: Create topic support (revisit based on v3 design)
>> KAFKA-339: Use multi-fetch for follower replication
>> KAFKA-350: Improve the highwatermark maintenance to handle failures
>> KAFKA-353: Tie Producer-side ack with high watermark and progress of
>> replicas
>>
>> The following jiras can be worked on in parallel and we welcome
>> contribution from the community.
>>
>> KAFKA-288: rework java producer API
>> KAFKA-289: reuse TopicData when sending produce request
>> KAFKA-354: refactor setter/getter in scala style
>> KAFKA-355: Move the highwatermark maintenance logic out of Log.
>> KAFKA-356: create a generic thread class
>>
>> Thanks,
>> Neha
>>
>
>
>
> --
>
> /*
> Joe Stein
> http://www.linkedin.com/in/charmalloc
> Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
> */

Re: Replication status

Posted by Joe Stein <cr...@gmail.com>.

I can start working on

KAFKA-354: refactor setter/getter in scala style

I will assign the JIRA to myself later tonight/tomorrow

On Fri, Jun 15, 2012 at 3:41 PM, Neha Narkhede <ne...@gmail.com>wrote:

> Hi,
>
> As of this week, we closed:
>
> KAFKA-335: Embedded controller
> KAFKA-341: Create a new single host system test to validate all
> replicas on 0.8 branch
>
> We have people signed up on the following jiras:
>
> KAFKA-329: Create topic support (revisit based on v3 design)
> KAFKA-339: Use multi-fetch for follower replication
> KAFKA-350: Improve the highwatermark maintenance to handle failures
> KAFKA-353: Tie Producer-side ack with high watermark and progress of
> replicas
>
> The following jiras can be worked on in parallel and we welcome
> contribution from the community.
>
> KAFKA-288: rework java producer API
> KAFKA-289: reuse TopicData when sending produce request
> KAFKA-354: refactor setter/getter in scala style
> KAFKA-355: Move the highwatermark maintenance logic out of Log.
> KAFKA-356: create a generic thread class
>
> Thanks,
> Neha
>



-- 

/*
Joe Stein
http://www.linkedin.com/in/charmalloc
Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
*/