Re: 0.8 behavior change: consumer "re-receives" last batch of messages in a topic?
I noticed the same thing. In 0.8.0 the offset passed to the fetch is where
you want to start, not where you left off. So the last offset read from the
previous batch is truly the 'last offset' so you need to save it and ask
for it +1. Otherwise you keep asking for that last offset, which is valid
so it keeps returning.
Be careful with the +1 logic. Don't keep adding 1 if you don't get
anything. It should always be 'last offset read +1'
I think this happened with the change from file-byte offsets to offset as a
On Wed, Mar 13, 2013 at 2:49 PM, Hargett, Phil <
[EMAIL PROTECTED]> wrote: