Hi Shafaq, "Yes" to your first question.
For second question that depends on what would you like to do when your request's offset is not valid. This is possible, for example, if your logs gets deleted according to retention policy and your last committed offset in ZK is within that deleted range. Setting auto.offset.reset means you will then start consuming from the beginning of the log if you encounter these cases. Detailed description of auto.offset.reset can be found at http://kafka.apache.org/documentation.html#consumerconfigs Guozhang On Tue, Nov 5, 2013 at 8:50 AM, Shafaq <s.abdullah...@gmail.com> wrote: > Hi, > > I wanted to control the commitOffset signal to ZK from High-level kafka > consumer. This will enable to process the message by consumer and incase > of failure the offset is not moved. > > If I do > auto.commit.enable= false > > and then use commitallOffset Api of high-level consumer, is that way to > achieve it? > > > > Also "auto.offset.reset"="smallest" need to be set inorder for consumer to > consume messages which are already published by broker. Is that correct? > > Please comment. > > > thanks! > > -- > Kind Regards, > Shafaq > -- -- Guozhang
