I added a couple of comments to the issue
https://issues.apache.org/jira/browse/KAFKA-364
(I was not certain whether you wanted comments on the mailing list, the
wiki page, or the issue?)
Thanks,
Ross
On Tue, Jun 19, 2012 at 10:09 AM, Neha Narkhede wrote:
> One of the goals of thinning the Kafka consumer client is removing the
> zookeeper client from the consumer. Without this, Kafka consumer
> client would depend on the stability of a zookeeper client.
If there's a stability issue with the zo
Chris,
One of the goals of thinning the Kafka consumer client is removing the
zookeeper client from the consumer. Without this, Kafka consumer
client would depend on the stability of a zookeeper client.
>> For a consumer that wants "Manual partition assignment" and "Manual offset
>> management",
On 06/12/2012 12:59 PM, Jay Kreps wrote:
>2. Try to replace the "simple consumer" and "high level consumer" with a
>single, general interface that has all the advantages of both.
I've read through the wiki pages but think I'm missing the forrest for
the trees.
For a consumer that wants "M
-dev@incubator.apache.org
Subject: Re: Consumer re-design proposal
Thanks for the feedback ! I moved it to
https://issues.apache.org/jira/browse/KAFKA-364, so that we can keep track
of these.
-Neha
On Thu, Jun 14, 2012 at 2:45 PM, Marcos Juarez wrote:
> Throwing a +1 on "Allow the con
Thanks for the feedback ! I moved it to
https://issues.apache.org/jira/browse/KAFKA-364, so that we can keep track
of these.
-Neha
On Thu, Jun 14, 2012 at 2:45 PM, Marcos Juarez wrote:
> Throwing a +1 on "Allow the consumer to reset its offset to some arbitrary
> value, and then write that offs
Throwing a +1 on "Allow the consumer to reset its offset to some arbitrary
value, and then write that offset into ZK".
We're currently running into a scenario where we would like to have 100%
reliability, and we're losing a few messages when a connection is broken, but
there were still a few me
I would like to throw in a couple use cases:
- Allow the new consumer to reset its offset to either the current
largest or smallest. This would be a great way to restart a process that
has fallen behind. The only way I know how to do this today, with the
high-level consumer, is to d
If nobody objects, we can create a separate consumer redesign branch. This
way, everyone can see the changes and progress.
Thanks,
Jun
On Mon, Jun 11, 2012 at 4:52 PM, Neha Narkhede wrote:
> Hi,
>
> Over the past few months, we've received quite a lot of feedback on the
> consumer side features
This is a great summary Neha. It would be good to get people's feedback on
this since we don't want to keep breaking api and
protocol compatibility here, so the hope is to really get it right this
time now that we have really seen all the use cases and live with the
output for a while. I think the
Hi,
Over the past few months, we've received quite a lot of feedback on the
consumer side features and design. Some of them are improvements to the
current consumer design and some are simply new feature/API requests. I
have attempted to write up the requirements that I've heard on this wiki -
htt
11 matches
Mail list logo
