Iterating and controlling Consumer.on messages about kafka-node HOT 8 CLOSED

You should try the latest version, fromBeginning is no longer support. If you want consume topic from the exact offset, you should set fromOffset true and also set the offset in payload, for example:

var payloads = [{ topic: 't', partition: 0, offset: offset_you_want }];
var consumer = new Consumer( client, payloads, { fromOffset: true });

If you just want consume the current message, the default settings should satisfy you.

from kafka-node.

Using the default settings causes

this.consumer.on('message', function (message) {
            console.log("Consumer Message",message);
 }); 

to continuously output the first message once a message exists in the partition:

Consumer Message 
{ 
topic: 'event-bus',
  value: '{type:\'PageView\',body:[]}',
  offset: 0,
  partition: 0,
  key: -1 }

from kafka-node.

Yes, what you see is the expected behavior of consumer with default settings. By default, consumer will consume message from the last commited offset when it start and consume whatever incoming message after start, it will automatically commit the offset too. If this not your use case, please explain here ^_^

from kafka-node.

I guess I was only expecting to consume each message once from the callback of Consumer.on, not have the last message consumed in a continuous loop. How can I block the consumption after one message until a new message is commited?

from kafka-node.

This seems a bug of consumer, I will look into it.

from kafka-node.

It should be fixed in this commit: fac599d
Please test it.

from kafka-node.

The !== undefined addition to lib/consumer.js fixed it! Thanks!

from kafka-node.

The !== undefined addition to lib/consumer.js fixed it! Thanks!

from kafka-node.