PM
To: users@kafka.apache.org
Subject: New Consumer APIs
Hi,
Would like to if New Consumer API is GAed.
Regards,
Rajeswari
Hi,
Would like to if New Consumer API is GAed.
Regards,
Rajeswari
; > However, I'd also like to understand your use case better. Are you trying
> > to use the consumer for group management (auto rebalancing) and at the
> same
> > time, control per partition commit()? In general, before proposing any
> > changes, I'd like to understand wh
the streams for things that consume
multiple inputs.
Not sure how much of that makes sense...
-Jay
On Fri, May 9, 2014 at 1:19 PM, Eric Sammer wrote:
> All:
>
> I've been going over the new consumer APIs and it seems like we're
> squishing a lot of different concerns toge
2014 at 8:42 AM, Timothy Chen wrote:
>
>> Also going to add that I know a per stream commit is a strong requirement
>> for folks I know using Kafka, and seen custom code done just to do so.
>>
>> Tim
>>
>> > On May 9, 2014, at 1:19 PM, Eric Sammer wrote:
&g
commit()? In general, before proposing any
> changes, I'd like to understand what you are hoping to achieve with the
> consumer APIs.
>
> Thanks,
> Neha
>
>
> On Fri, May 9, 2014 at 1:19 PM, Eric Sammer
> wrote:
>
> > All:
> >
> > I've been
een going over the new consumer APIs and it seems like we're
> squishing a lot of different concerns together into a single class. The
> scope of the new Consumer is kind of all over the place. Managing the
> lifecycle - and especially the thread safety - seems challenging.
> Specif
; > All:
> >
> > I've been going over the new consumer APIs and it seems like we're
> > squishing a lot of different concerns together into a single class. The
> > scope of the new Consumer is kind of all over the place. Managing the
> > lifecycle - and especia
osing any
changes, I'd like to understand what you are hoping to achieve with the
consumer APIs.
Thanks,
Neha
On Fri, May 9, 2014 at 1:19 PM, Eric Sammer wrote:
> All:
>
> I've been going over the new consumer APIs and it seems like we're
> squishing a lot of differen
Also going to add that I know a per stream commit is a strong requirement for
folks I know using Kafka, and seen custom code done just to do so.
Tim
> On May 9, 2014, at 1:19 PM, Eric Sammer wrote:
>
> All:
>
> I've been going over the new consumer APIs and it seems like
All:
I've been going over the new consumer APIs and it seems like we're
squishing a lot of different concerns together into a single class. The
scope of the new Consumer is kind of all over the place. Managing the
lifecycle - and especially the thread safety - seems challenging.
Sp
Hi Neha,
How will new Consumer help us with implementing following use case?
We have heartbeat as one of topics and all application servers publish
metric to this topic. We have to meet near real-time consume SLA (less
than 30 seconds).
1) We would like to find out what is latest message per
Why cant we pass a callback in subscribe itself?
Mainly because it will make the processing kind of awkward since you need
to access the other consumer APIs while processing the messages. Your
suggestion does point out a problem with the poll() API though. Here is the
initial proposal of the poll(
Was trying to understand when we have subscribe then why poll is a separate
API.Why cant we pass a callback in subscribe itself?
On Mon, Apr 7, 2014 at 9:51 PM, Neha Narkhede wrote:
> Hi,
>
> I'm looking for people to review the new consumers APIs. Patch is posted at
> https://issues.apache.org/
Hi,
I'm looking for people to review the new consumers APIs. Patch is posted at
https://issues.apache.org/jira/browse/KAFKA-1328
Thanks,
Neha
15 matches
Mail list logo
