I think my previous answer was not complete thanks to Tao's reminder: in
fact, the retention is controlled both on the client and server side,
1) users can set the retention time period on the OffsetCommitRequest (in
latest version v2).
2) in the current Java client implementation, it is always se
Hi Mathieu,
I have a PR against 0.10.0 branch to backport the bug fix plus some
refactoring, feel free to try it out:
https://github.com/apache/kafka/pull/1735
Guozhang
On Wed, Aug 10, 2016 at 2:28 PM, Mathieu Fenniak <
mathieu.fenn...@replicon.com> wrote:
> Hi Guozhang,
>
> Yes, it does
Hi Guozhang,
Thanks for replies. And which is the expiration parameter? Can I config it
on broker or on consumer?
Thanks and Regards
Yuanjia Li
From: Guozhang Wang
Date: 2016-08-13 03:05
To: users@kafka.apache.org
Subject: Re: kafka-consumer-groups.sh delete group with new-consumer
Hi Yu
Yes, the event will be broadcast live (stream URL will be posted an hour
before the meetup) however we don't have facility to take Q&A over the
stream at this time. This of it as read-only :).
On Sat, Aug 13, 2016 at 2:53 PM, Felipe Santos wrote:
> Hi,
>
> The event will be broadcast live?
>
>
Hi,
If I have a running consumer assigned to a topic-partition (either with
'subscribe' or with 'assign'), can I retrieve the latest available offset
and the latest committed offset of that topic-partition from another
process (another consumer), without causing rebalancing?
Thanks,
Alex
I think this will help.
Thanks.
On 8/12/16, 6:16 PM, "Guozhang Wang" wrote:
>Hello Sean,
>
>We are adding a background thread doing heartbeats as part of the adopted
>KIP-62:
>https://cwiki.apache.org/confluence/display/KAFKA/KIP-62%3A+Allow+consumer+to+send+heartbeats+from+a+background+thre
