commitSync with new Subscriber API

[Kevin Carr <ks...@gmail.com>]

I am using the new Subscriber API and I poll.  The poll returns 2005
messages.  I process 2 of them, and then set the offset to the 2nd message
offset that I processed.

I then call commitSync with the TopicPartition and this new offset.  When I
list the group with the command line tool, it always shows the original
offset.

Am I doing something wrong?

Re: commitSync with new Subscriber API

[Kevin Carr <ks...@gmail.com>]

I was using a FastMap from javalution.  It seemed to have a problem with
isEmpty inside the commitSync code.

I changed to use a regular HashMap and everything is fine now.  Sorry for
the post.

On Thu, Dec 10, 2015, 9:33 PM Guozhang Wang <wa...@gmail.com> wrote:

> Can you paste your list group command line here?
>
> Guozhang
>
> On Thu, Dec 10, 2015 at 2:45 PM, Kevin Carr <ks...@gmail.com> wrote:
>
> > I am using the new Subscriber API and I poll.  The poll returns 2005
> > messages.  I process 2 of them, and then set the offset to the 2nd
> message
> > offset that I processed.
> >
> > I then call commitSync with the TopicPartition and this new offset.
> When I
> > list the group with the command line tool, it always shows the original
> > offset.
> >
> > Am I doing something wrong?
> >
>
>
>
> --
> -- Guozhang
>

Re: commitSync with new Subscriber API

[Guozhang Wang <wa...@gmail.com>]

Can you paste your list group command line here?

Guozhang

On Thu, Dec 10, 2015 at 2:45 PM, Kevin Carr <ks...@gmail.com> wrote:

> I am using the new Subscriber API and I poll.  The poll returns 2005
> messages.  I process 2 of them, and then set the offset to the 2nd message
> offset that I processed.
>
> I then call commitSync with the TopicPartition and this new offset.  When I
> list the group with the command line tool, it always shows the original
> offset.
>
> Am I doing something wrong?
>



-- 
-- Guozhang