KafkaConsumerFlowlet's getDefaultOffset does not work as advertised
Description
Release Notes
None
Activity
Show:
Ali Anwar January 30, 2015 at 2:26 AM
Sreevatsan Raman January 27, 2015 at 10:45 PM
Assigning to Ali to take a look.
Sreevatsan Raman December 23, 2014 at 11:50 PM
Not critical. Moving it to 2.7.0
Ali Anwar November 30, 2014 at 7:48 PM
That would be one thing that prevents it from working, but also we dont save consumerInfos if no messages arrive either.
Terence Yim November 30, 2014 at 5:19 PM
It sounds like it was caused by the latest addition of the if (count == 0) check?
Fixed
Pinned fields
Click on the next to a field label to start pinning.
Created November 30, 2014 at 1:51 AM
Updated March 27, 2015 at 7:30 PM
Resolved January 30, 2015 at 2:26 AM
In Kafka07ConsumerFlowlet, the documentation claims that getDefaultOffset can be overridden, to return a value from which to start consuming.
It marks -1L as a code to start from the latest offset. However, this doesn't correctly make the ConsumerFlowlet start from the latest offset.
This needs further investigation, but when returning -1L, no events get processed by the flowlet, even if you send new events into Kafka.