Skip to main content

The Kafka Series (part 4): implementing a consumer in Java

In part 3 of this series we have implemented a simple Kafka producer using the provided Java APIs. Now let's learn how to implement a consumer for the produced messages. The Kafka release I am referring to is always the 0.9.0.1.
Same as for the producer, I suggest to use Maven: this way you have to add only one direct dependency through the POM file:

<dependency>
    <groupId>org.apache.kafka</groupId>
    <artifactId>kafka-clients</artifactId>
    <version>0.9.0.1</version>
</dependency>


Then create a new class called, for example, SimpleKafkaConsumer:

public class SimpleKafkaConsumer implements Runnable {
    KafkaConsumer<String, String> consumer;


It implements the java.lang.Runnable interface and has a single instance variable, consumer, which type is org.apache.kafka.clients.consumer.KafkaConsumer<K,V>. It is the client that consumes records from a Kafka cluster. It isn't thread-safe.
In the initialization method of the class you have to setup the properties required for the consumer configuration. Here I am reporting a small list including the mandatory ones only:

Properties props = new Properties();
props.put("bootstrap.servers", "bootstrap1.blogspot.com:9092, bootstrap2.blogspot.com:9092");
props.put("group.id", "ktesting");
props.put("enable.auto.commit", "true");
props.put("auto.commit.interval.ms", "1000");
props.put("session.timeout.ms", "30000");
props.put("key.deserializer", "org.apache.kafka.common.serialization.StringDeserializer");
props.put("value.deserializer", "org.apache.kafka.common.serialization.StringDeserializer");


Here's the meaning of the properties used in the example code above (a future post of this series will walk through almost all of the available properties to configure a consumer):

  • bootstrap.servers: a list of comma separated host/port pairs to use for establishing the initial connection to the Kafka cluster. No need to specify all of the nodes of the cluster. You need to add more than one just in case the first one in the list should be down at connection time.
  • group.id: uniquely identifies the group of consumer processes to which this consumer belongs.
  • enable.auto.commit: if true, periodically commit to ZooKeeper the offset of messages already fetched by the consumer.
  • auto.commit.intervals.ms: the frequency (in milliseconds) that the consumer offsets are committed to zookeeper. It is used only when enable.auto.commit is true.
  • session.timeout.ms: the timeout (in milliseconds) used to detect failures.
  • key.deserializer: defines the class for a message key that implements the org.apache.kafka.common.serialization.Serializer interface. In the code example above we used the org.apache.kafka.common.serialization.StringSerializer class.
  • value.deserializer: defines the class for a message value that implements the org.apache.kafka.common.serialization.Serializer  interface. In the code example above we used the org.apache.kafka.common.serialization.StringSerializer class.
Now you can create an instance of the KafkaConsumer client using the settings above:

consumer = new KafkaConsumer<String, String>(props);

And finally you can implement a method to consume messages subscribing to one or more topics:

public void subscribeToTopics() {
    consumer.subscribe(Arrays.asList("kafkatesting"));
    while(true) {
         ConsumerRecords<String, String> records = consumer.poll(100);
         for(ConsumerRecord<String, String> record : records)
              System.out.printf("offset = %d, key = %s, value = %s", record.offset(), record.key(), record.value());

         // Do something with the messages
    }
}


This is of course a very basic implementation: once the application consumes the messages you can do whatever you want with them.
In this example the subscribeToTopics() method is called in the java.lang.Runnable.run() method implementation:

public void run() {
    subscribeToTopics();
}


What's next?

In the next part of this series we will have a detailed look at all of the available configuration properties for a producer.

Comments

Popular posts from this blog

Exporting InfluxDB data to a CVS file

Sometimes you would need to export a sample of the data from an InfluxDB table to a CSV file (for example to allow a data scientist to do some offline analysis using a tool like Jupyter, Zeppelin or Spark Notebook). It is possible to perform this operation through the influx command line client. This is the general syntax: sudo /usr/bin/influx -database '<database_name>' -host '<hostname>' -username '<username>'  -password '<password>' -execute 'select_statement' -format '<format>' > <file_path>/<file_name>.csv where the format could be csv , json or column . Example: sudo /usr/bin/influx -database 'telegraf' -host 'localhost' -username 'admin'  -password '123456789' -execute 'select * from mem' -format 'csv' > /home/googlielmo/influxdb-export/mem-export.csv

jOOQ: code generation in Eclipse

jOOQ allows code generation from a database schema through ANT tasks, Maven and shell command tools. But if you're working with Eclipse it's easier to create a new Run Configuration to perform this operation. First of all you have to write the usual XML configuration file for the code generation starting from the database: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <configuration xmlns="http://www.jooq.org/xsd/jooq-codegen-2.0.4.xsd">   <jdbc>     <driver>oracle.jdbc.driver.OracleDriver</driver>     <url>jdbc:oracle:thin:@dbhost:1700:DBSID</url>     <user>DB_FTRS</user>     <password>password</password>   </jdbc>   <generator>     <name>org.jooq.util.DefaultGenerator</name>     <database>       <name>org.jooq.util.oracle.OracleDatabase</name>     ...

Using Rapids cuDF in a Colab notebook

During last Spark+AI Summit Europe 2019 I had a chance to attend a talk from Miguel Martinez  who was presenting Rapids , the new Open Source framework from NVIDIA for GPU accelerated end-to-end Data Science and Analytics. Fig. 1 - Overview of the Rapids eco-system Rapids is a suite of Open Source libraries: cuDF cuML cuGraph cuXFilter I enjoied the presentation and liked the idea of this initiative, so I wanted to start playing with the Rapids libraries in Python on Colab , starting from cuDF, but the first attempt came with an issue that I eventually solved. So in this post I am going to share how I fixed it, with the hope it would be useful to someone else running into the same blocker. I am assuming here you are already familiar with Google Colab. I am using Python 3.x as Python 2 isn't supported by Rapids. Once you have created a new notebook in Colab, you need to check if the runtime for it is set to use Python 3 and uses a GPU as hardware accelerator. You...