Well, resetting could follow the partition ownership where only owned
partitions can be reset by any one consumer. There's definitely a case for
consumer applications that are more about observing frequencies rather than
total aggregation and so are typically interested in last couple of seconds
/
It's more than that. For example, what if 2 consumers want to set different
offsets for the same partition?
Jun
On Tue, Nov 13, 2012 at 4:08 PM, Michal Haris wrote:
> Of course assuming that none of the consumers in the group are interested
> in the missed messages in such case.
> On Nov 12, 201
Of course assuming that none of the consumers in the group are interested
in the missed messages in such case.
On Nov 12, 2012 6:03 AM, "Jun Rao" wrote:
> It's easy if there is only a single consumer in the group. In general,
> however, there could be multiple consumers in the same group. So, som
It's easy if there is only a single consumer in the group. In general,
however, there could be multiple consumers in the same group. So, some kind
of coordination is needed.
Thanks,
Jun
On Sat, Nov 10, 2012 at 6:41 AM, Michal Haris wrote:
> Found it in archives, autooffset.reset is only used wh
Found it in archives, autooffset.reset is only used when the consumer
registering first time or the last committed offset is out-of-range, so
that means that we have to create direct connection to the zookeeper and
set/delete the /consumer/xyz/offset/topic123/*-* before starting the
consumer to get
Really? So what does the autooffset.reset=largest do ?
On Nov 9, 2012 3:30 PM, "Jun Rao" wrote:
> Bob,
>
> The high level consumer doesn't support resetting the starting offset right
> now. We will look into that post 0.8 as part of the consumer redesign.
>
> Thanks,
>
> Jun
>
>
> On Fri, Nov 9,
Bob,
The high level consumer doesn't support resetting the starting offset right
now. We will look into that post 0.8 as part of the consumer redesign.
Thanks,
Jun
On Fri, Nov 9, 2012 at 5:04 AM, Bob Cotton wrote:
> We have a topic whose consumers, on startup, only need to consume from the
>
We have a topic whose consumers, on startup, only need to consume from the
head of the topic. They don't need to consume old messages they may have
missed.
We would like to use the high-level consumer, as the API is a bit simpler.
Is there a way to reset the current offsets for the high-level con
