Kafka - Consumer

> Data Integration Tool (ETL/ELT) > Kafka (Event Hub)

1 - About

A consumer.

A sink connector is a consumer.

Advertising

3 - Management

3.1 - console utility

3.2 - Configuration

The configs can be overridden by prefixing them with consumer.

For example:

consumer.max.partition.fetch.bytes=10485760

http://kafka.apache.org/documentation.html#newconsumerconfigs

3.3 - Offset

The only metadata retained on a per-consumer basis is the offset or position of that consumer in the log.

This offset is controlled by the consumer: normally a consumer will advance its offset linearly as it reads records, but, in fact, since the position is controlled by the consumer it can consume records in any order it likes.

For example a consumer can reset to an older offset to reprocess data from the past or skip ahead to the most recent record and start consuming from “now”.

Advertising

3.4 - Group

The consumer group is used for coordination between consumers. See Kafka - Consumer Group

3.5 - Message Read Status

When all in-sync replicas have acknowledged the write, then the message is considered committed, which makes it available for reading. This ensures that messages cannot be lost by a broker failure after they have already been read.

4 - Documentation / Reference