It may be a minority, I can't tell yet. But in some apps we need to know that
a consumer, who is assigned a single partition, will get all data about a
subset of users.
This is way more flexible than multiple topics since we still have the benefits
of partition reassignment, load balancing bet
Using the high level consumer, each consumer in the group can call iter.next ()
in a loop until they get the number of messages you need.
—
Sent from Mailbox
On Thu, Oct 16, 2014 at 10:18 AM, Josh J wrote:
> hi,
> How do I read N items from a topic? I also would like to do this for a
> consume
Its using the sync producer without waiting for any broker to acknowledge the
write. This explains the lack of errors you are seeing.
—
Sent from Mailbox
On Fri, Oct 17, 2014 at 3:15 PM, Mohit Anchlia
wrote:
> Little confused :) From one of the examples I am using property
> request.required.
