How to connect Pulsar to database

This tutorial provides a hands-on look at how you can move data out of Pulsar without writing a single line of code.

It is helpful to review the concepts for Pulsar I/O with running the steps in this guide to gain a deeper understanding.

At the end of this tutorial, you are able to:

• Connect Pulsar to Cassandra

• Connect Pulsar to MySQL

tip

• These instructions assume you are running Pulsar in standalone mode. However, all the commands used in this tutorial can be used in a multi-nodes Pulsar cluster without any changes.
• All the instructions are assumed to run at the root directory of a Pulsar binary distribution.

Install Pulsar and built-in connector

Before connecting Pulsar to a database, you need to install Pulsar and the desired built-in connector.

For more information about how to install a standalone Pulsar and built-in connectors, see here.

Start Pulsar standalone

1. Start Pulsar locally.

   
   bin/pulsar standalone
   

   All the components of a Pulsar service are start in order.

   You can curl those pulsar service endpoints to make sure Pulsar service is up running correctly.

2. Check Pulsar binary protocol port.

   
   telnet localhost 6650
   

3. Check Pulsar Function cluster.

   
   curl -s http://localhost:8080/admin/v2/worker/cluster
   

   Example output

   
   [{"workerId":"c-standalone-fw-localhost-6750","workerHostname":"localhost","port":6750}]
   

4. Make sure a public tenant and a default namespace exist.

   
   curl -s http://localhost:8080/admin/v2/namespaces/public
   

   Example output

   
   ["public/default","public/functions"]
   

5. All built-in connectors should be listed as available.

   
   curl -s http://localhost:8080/admin/v2/functions/connectors
   

   Example outoupt

   
   [{"name":"aerospike","description":"Aerospike database sink","sinkClass":"org.apache.pulsar.io.aerospike.AerospikeStringSink"},{"name":"cassandra","description":"Writes data into Cassandra","sinkClass":"org.apache.pulsar.io.cassandra.CassandraStringSink"},{"name":"kafka","description":"Kafka source and sink connector","sourceClass":"org.apache.pulsar.io.kafka.KafkaStringSource","sinkClass":"org.apache.pulsar.io.kafka.KafkaBytesSink"},{"name":"kinesis","description":"Kinesis sink connector","sinkClass":"org.apache.pulsar.io.kinesis.KinesisSink"},{"name":"rabbitmq","description":"RabbitMQ source connector","sourceClass":"org.apache.pulsar.io.rabbitmq.RabbitMQSource"},{"name":"twitter","description":"Ingest data from Twitter firehose","sourceClass":"org.apache.pulsar.io.twitter.TwitterFireHose"}]
   

   If an error occurs when starting Pulsar service, you may see an exception at the terminal running pulsar/standalone, or you can navigate to the logs directory under the Pulsar directory to view the logs.

Connect Pulsar to Cassandra

This section demonstrates how to connector Pulsar to Cassandra.

tip

• Make sure you have Docker installed. If you do not have one, see install Docker.
• The Cassandra sink connector reads messages from Pulsar topics and writes the messages into Cassandra tables. For more information, see Cassandra sink connector.

Setup a Cassandra cluster

This example uses cassandra Docker image to start a single-node Cassandra cluster in Docker.

1. Start a Cassandra cluster.

   
   docker run -d --rm --name=cassandra -p 9042:9042 cassandra:3.11
   
   note

   Before moving to the next steps, make sure the Cassandra cluster is running.

2. Make sure the Docker process is running.

   
   docker ps
   

3. Check the Cassandra logs to make sure the Cassandra process is running as expected.

   
   docker logs cassandra
   

4. Check the status of the Cassandra cluster.

   
   docker exec cassandra nodetool status
   

   Example output

   
   Datacenter: datacenter1
   =======================
   Status=Up/Down
   |/ State=Normal/Leaving/Joining/Moving
   --  Address     Load       Tokens       Owns (effective)  Host ID                               Rack
   UN  172.17.0.2  103.67 KiB  256          100.0%            af0e4b2f-84e0-4f0b-bb14-bd5f9070ff26  rack1
   

5. Use cqlsh to connect to the Cassandra cluster.

   
   $ docker exec -ti cassandra cqlsh localhost
   Connected to Test Cluster at localhost:9042.
   [cqlsh 5.0.1 | Cassandra 3.11.2 | CQL spec 3.4.4 | Native protocol v4]
   Use HELP for help.
   cqlsh>
   

6. Create a keyspace pulsar_test_keyspace.

   
   cqlsh> CREATE KEYSPACE pulsar_test_keyspace WITH replication = {'class':'SimpleStrategy', 'replication_factor':1};
   

7. Create a table pulsar_test_table.

   
   cqlsh> USE pulsar_test_keyspace;
   cqlsh:pulsar_test_keyspace> CREATE TABLE pulsar_test_table (key text PRIMARY KEY, col text);
   

Configure a Cassandra sink

Now that we have a Cassandra cluster running locally.

In this section, you need to configure a Cassandra sink connector.

To run a Cassandra sink connector, you need to prepare a configuration file including the information that Pulsar connector runtime needs to know.

For example, how Pulsar connector can find the Cassandra cluster, what is the keyspace and the table that Pulsar connector uses for writing Pulsar messages to, and so on.

You can create a configuration file through one of the following methods.

• JSON

  
  {
      "roots": "localhost:9042",
      "keyspace": "pulsar_test_keyspace",
      "columnFamily": "pulsar_test_table",
      "keyname": "key",
      "columnName": "col"
  }
  

• YAML

  
  configs:
      roots: "localhost:9042"
      keyspace: "pulsar_test_keyspace"
      columnFamily: "pulsar_test_table"
      keyname: "key"
      columnName: "col"
  

For more information, see Cassandra sink connector.

Create a Cassandra sink

You can use the Connector Admin CLI to create a sink connector and perform other operations on them.

Run the following command to create a Cassandra sink connector with sink type cassandra and the config file examples/cassandra-sink.yml created previously.

Note

The sink-type parameter of the currently built-in connectors is determined by the setting of the name parameter specified in the pulsar-io.yaml file.

bin/pulsar-admin sinks create \
    --tenant public \
    --namespace default \
    --name cassandra-test-sink \
    --sink-type cassandra \
    --sink-config-file examples/cassandra-sink.yml \
    --inputs test_cassandra

Once the command is executed, Pulsar creates the sink connector cassandra-test-sink.

This sink connector runs as a Pulsar Function and writes the messages produced in the topic test_cassandra to the Cassandra table pulsar_test_table.

Inspect a Cassandra sink

You can use the Connector Admin CLI to monitor a connector and perform other operations on it.

• Get the information of a Cassandra sink.

  
  bin/pulsar-admin sinks get \
    --tenant public \
    --namespace default \
    --name cassandra-test-sink
  

  Example output

  
  {
  "tenant": "public",
  "namespace": "default",
  "name": "cassandra-test-sink",
  "className": "org.apache.pulsar.io.cassandra.CassandraStringSink",
  "inputSpecs": {
    "test_cassandra": {
      "isRegexPattern": false
    }
  },
  "configs": {
    "roots": "localhost:9042",
    "keyspace": "pulsar_test_keyspace",
    "columnFamily": "pulsar_test_table",
    "keyname": "key",
    "columnName": "col"
  },
  "parallelism": 1,
  "processingGuarantees": "ATLEAST_ONCE",
  "retainOrdering": false,
  "autoAck": true,
  "archive": "builtin://cassandra"
  }
  

• Check the status of a Cassandra sink.

  
  bin/pulsar-admin sinks status \
    --tenant public \
    --namespace default \
    --name cassandra-test-sink
  

  Example output

  
  {
  "numInstances" : 1,
  "numRunning" : 1,
  "instances" : [ {
    "instanceId" : 0,
    "status" : {
      "running" : true,
      "error" : "",
      "numRestarts" : 0,
      "numReadFromPulsar" : 0,
      "numSystemExceptions" : 0,
      "latestSystemExceptions" : [ ],
      "numSinkExceptions" : 0,
      "latestSinkExceptions" : [ ],
      "numWrittenToSink" : 0,
      "lastReceivedTime" : 0,
      "workerId" : "c-standalone-fw-localhost-8080"
    }
  } ]
  }
  

Verify a Cassandra sink

1. Produce some messages to the input topic of the Cassandra sink test_cassandra.

   
   for i in {0..9}; do bin/pulsar-client produce -m "key-$i" -n 1 test_cassandra; done
   

2. Inspect the status of the Cassandra sink test_cassandra.

   
   bin/pulsar-admin sinks status \
       --tenant public \
       --namespace default \
       --name cassandra-test-sink
   

   You can see 10 messages are processed by the Cassandra sink test_cassandra.

   Example output

   
   {
     "numInstances" : 1,
     "numRunning" : 1,
     "instances" : [ {
       "instanceId" : 0,
       "status" : {
         "running" : true,
         "error" : "",
         "numRestarts" : 0,
         "numReadFromPulsar" : 10,
         "numSystemExceptions" : 0,
         "latestSystemExceptions" : [ ],
         "numSinkExceptions" : 0,
         "latestSinkExceptions" : [ ],
         "numWrittenToSink" : 10,
         "lastReceivedTime" : 1551685489136,
         "workerId" : "c-standalone-fw-localhost-8080"
       }
     } ]
   }
   

3. Use cqlsh to connect to the Cassandra cluster.

   
   docker exec -ti cassandra cqlsh localhost
   

4. Check the data of the Cassandra table pulsar_test_table.

   
   cqlsh> use pulsar_test_keyspace;
   cqlsh:pulsar_test_keyspace> select * from pulsar_test_table;
   
   key    | col
   --------+--------
    key-5 |  key-5
    key-0 |  key-0
    key-9 |  key-9
    key-2 |  key-2
    key-1 |  key-1
    key-3 |  key-3
    key-6 |  key-6
    key-7 |  key-7
    key-4 |  key-4
    key-8 |  key-8
   

Delete a Cassandra Sink

You can use the Connector Admin CLI to delete a connector and perform other operations on it.

bin/pulsar-admin sinks delete \
    --tenant public \
    --namespace default \
    --name cassandra-test-sink

Connect Pulsar to MySQL

This section demonstrates how to connector Pulsar to MySQL.

tip

• Make sure you have Docker installed. If you do not have one, see install Docker.
• The JDBC sink connector pulls messages from Pulsar topics and persists the messages to MySQL or SQlite. For more information, see JDBC sink connector.

Setup a MySQL cluster

This example uses the MySQL 5.7 docker image to start a single-node MySQL cluster in Docker.

1. Pull the MySQL 5.7 image from Docker.

   
   $ docker pull mysql:5.7
   

2. Start MySQL.

   
   $ docker run -d -it --rm \
   --name pulsar-mysql \
   -p 3306:3306 \
   -e MYSQL_ROOT_PASSWORD=jdbc \
   -e MYSQL_USER=mysqluser \
   -e MYSQL_PASSWORD=mysqlpw \
   mysql:5.7
   

   Tip

   Flag	Description	This example
   -d	To start a container in detached mode.	/
   -it	Keep STDIN open even if not attached and allocate a terminal.	/
   --rm	Remove the container automatically when it exits.	/
   -name	Assign a name to the container.	This example specifies pulsar-mysql for the container.
   -p	Publish the port of the container to the host.	This example publishes the port 3306 of the container to the host.
   -e	Set environment variables.	This example sets the following variables: - The password for the root user is jdbc. - The name for the normal user is mysqluser. - The password for the normal user is mysqlpw.

   tip

   For more information about Docker commands, see Docker CLI.

3. Check if MySQL has been started successfully.

   
   $ docker logs -f pulsar-mysql
   

   MySQL has been started successfully if the following message appears.

   
   2019-05-11T10:40:58.709964Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.
   2019-05-11T10:40:58.710155Z 0 [Warning] CA certificate ca.pem is self signed.
   2019-05-11T10:40:58.711921Z 0 [Note] Server hostname (bind-address): '*'; port: 3306
   2019-05-11T10:40:58.711985Z 0 [Note] IPv6 is available.
   2019-05-11T10:40:58.712695Z 0 [Note]   - '::' resolves to '::';
   2019-05-11T10:40:58.712742Z 0 [Note] Server socket created on IP: '::'.
   2019-05-11T10:40:58.714334Z 0 [Warning] Insecure configuration for --pid-file: Location '/var/run/mysqld' in the path is accessible to all OS users. Consider choosing a different directory.
   2019-05-11T10:40:58.723802Z 0 [Note] Event Scheduler: Loaded 0 events
   2019-05-11T10:40:58.724200Z 0 [Note] mysqld: ready for connections.
   Version: '5.7.26'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server (GPL)
   

4. Access to MySQL.

   
   $ docker exec -it pulsar-mysql /bin/bash
   mysql -h localhost -uroot -pjdbc
   

5. Create a MySQL table pulsar_mysql_jdbc_sink.

   
   $ create database pulsar_mysql_jdbc_sink;
   
   $ use pulsar_mysql_jdbc_sink;
   
   $ create table if not exists pulsar_mysql_jdbc_sink
   (
   id INT AUTO_INCREMENT,
   name VARCHAR(255) NOT NULL,
   primary key (id)
   )
   engine=innodb;
   

Configure a JDBC sink

Now that we have a MySQL running locally.

In this section, you need to configure a JDBC sink connector.

1. Add a configuration file.

   To run a JDBC sink connector, you need to prepare a YAML configuration file including the information that Pulsar connector runtime needs to know.

   For example, how Pulsar connector can find the MySQL cluster, what is the JDBC URL and the table that Pulsar connector uses for writing messages to.

   Create a pulsar-mysql-jdbc-sink.yaml file, copy the following contents to this file, and place the file in the pulsar/connectors folder.

   
   configs:
     userName: "root"
     password: "jdbc"
     jdbcUrl: "jdbc:mysql://127.0.0.1:3306/pulsar_mysql_jdbc_sink"
     tableName: "pulsar_mysql_jdbc_sink"
   

2. Create a schema.

   Create a avro-schema file, copy the following contents to this file, and place the file in the pulsar/connectors folder.

   
   {
     "type": "AVRO",
     "schema": "{\"type\":\"record\",\"name\":\"Test\",\"fields\":[{\"name\":\"id\",\"type\":[\"null\",\"int\"]},{\"name\":\"name\",\"type\":[\"null\",\"string\"]}]}",
     "properties": {}
   }
   
   tip

   For more information about AVRO, see Apache Avro.

3. Upload a schema to a topic.

   This example uploads the avro-schema schema to the pulsar-mysql-jdbc-sink-topic topic.

   
   $ bin/pulsar-admin schemas upload pulsar-mysql-jdbc-sink-topic -f ./connectors/avro-schema
   

4. Check if the schema has been uploaded successfully.

   
   $ bin/pulsar-admin schemas get pulsar-mysql-jdbc-sink-topic
   

   The schema has been uploaded successfully if the following message appears.

   
   {"name":"pulsar-mysql-jdbc-sink-topic","schema":"{\"type\":\"record\",\"name\":\"Test\",\"fields\":[{\"name\":\"id\",\"type\":[\"null\",\"int\"]},{\"name\":\"name\",\"type\":[\"null\",\"string\"]}]}","type":"AVRO","properties":{}}
   

Create a JDBC sink

You can use the Connector Admin CLI to create a sink connector and perform other operations on it.

This example creates a sink connector and specifies the desired information.

$ bin/pulsar-admin sinks create \
--archive ./connectors/pulsar-io-jdbc-2.5.1.nar \
--inputs pulsar-mysql-jdbc-sink-topic \
--name pulsar-mysql-jdbc-sink \
--sink-config-file ./connectors/pulsar-mysql-jdbc-sink.yaml \
--parallelism 1

Once the command is executed, Pulsar creates a sink connector pulsar-mysql-jdbc-sink.

This sink connector runs as a Pulsar Function and writes the messages produced in the topic pulsar-mysql-jdbc-sink-topic to the MySQL table pulsar_mysql_jdbc_sink.

Tip

Flag	Description	This example
--archive	The path to the archive file for the sink.	pulsar-io-jdbc-2.5.1.nar
--inputs	The input topic(s) of the sink. Multiple topics can be specified as a comma-separated list.
--name	The name of the sink.	pulsar-mysql-jdbc-sink
--sink-config-file	The path to a YAML config file specifying the configuration of the sink.	pulsar-mysql-jdbc-sink.yaml
--parallelism	The parallelism factor of the sink. For example, the number of sink instances to run.	1

tip

For more information about pulsar-admin sinks create options, see here.

The sink has been created successfully if the following message appears.

"Created successfully"

Inspect a JDBC sink

You can use the Connector Admin CLI to monitor a connector and perform other operations on it.

• List all running JDBC sink(s).

  
  $ bin/pulsar-admin sinks list \
  --tenant public \
  --namespace default
  
  tip

  For more information about pulsar-admin sinks list options, see here.

  The result shows that only the mysql-jdbc-sink sink is running.

  
  [
  "pulsar-mysql-jdbc-sink"
  ]
  

• Get the information of a JDBC sink.

  
  $ bin/pulsar-admin sinks get \
  --tenant public \
  --namespace default \
  --name pulsar-mysql-jdbc-sink
  
  tip

  For more information about pulsar-admin sinks get options, see here.

  The result shows the information of the sink connector, including tenant, namespace, topic and so on.

  
  {
  "tenant": "public",
  "namespace": "default",
  "name": "pulsar-mysql-jdbc-sink",
  "className": "org.apache.pulsar.io.jdbc.JdbcAutoSchemaSink",
  "inputSpecs": {
    "pulsar-mysql-jdbc-sink-topic": {
      "isRegexPattern": false
    }
  },
  "configs": {
    "password": "jdbc",
    "jdbcUrl": "jdbc:mysql://127.0.0.1:3306/pulsar_mysql_jdbc_sink",
    "userName": "root",
    "tableName": "pulsar_mysql_jdbc_sink"
  },
  "parallelism": 1,
  "processingGuarantees": "ATLEAST_ONCE",
  "retainOrdering": false,
  "autoAck": true
  }
  

• Get the status of a JDBC sink

  
  $ bin/pulsar-admin sinks status \
  --tenant public \
  --namespace default \
  --name pulsar-mysql-jdbc-sink
  
  tip

  For more information about pulsar-admin sinks status options, see here.

  The result shows the current status of sink connector, including the number of instance, running status, worker ID and so on.

  
  {
  "numInstances" : 1,
  "numRunning" : 1,
  "instances" : [ {
    "instanceId" : 0,
    "status" : {
      "running" : true,
      "error" : "",
      "numRestarts" : 0,
      "numReadFromPulsar" : 0,
      "numSystemExceptions" : 0,
      "latestSystemExceptions" : [ ],
      "numSinkExceptions" : 0,
      "latestSinkExceptions" : [ ],
      "numWrittenToSink" : 0,
      "lastReceivedTime" : 0,
      "workerId" : "c-standalone-fw-192.168.2.52-8080"
    }
  } ]
  }
  

Stop a JDBC sink

You can use the Connector Admin CLI to stop a connector and perform other operations on it.

$ bin/pulsar-admin sinks stop \
--tenant public \
--namespace default \
--name pulsar-mysql-jdbc-sink \
--instance-id 0

tip

For more information about pulsar-admin sinks stop options, see here.

The sink instance has been stopped successfully if the following message disappears.

"Stopped successfully"

Restart a JDBC sink

You can use the Connector Admin CLI to restart a connector and perform other operations on it.

$ bin/pulsar-admin sinks restart \
--tenant public \
--namespace default \
--name pulsar-mysql-jdbc-sink \
--instance-id 0

tip

For more information about pulsar-admin sinks restart options, see here.

The sink instance has been started successfully if the following message disappears.

"Started successfully"

tip

• Optionally, you can run a standalone sink connector using pulsar-admin sinks localrun options. Note that pulsar-admin sinks localrun options runs a sink connector locally, while pulsar-admin sinks start options starts a sink connector in a cluster.
• For more information about pulsar-admin sinks localrun options, see here.

Update a JDBC sink

You can use the Connector Admin CLI to update a connector and perform other operations on it.

This example updates the parallelism of the pulsar-mysql-jdbc-sink sink connector to 2.

$ bin/pulsar-admin sinks update \
--name pulsar-mysql-jdbc-sink \
--parallelism 2

tip

For more information about pulsar-admin sinks update options, see here.

The sink connector has been updated successfully if the following message disappears.

"Updated successfully"

This example double-checks the information.

$ bin/pulsar-admin sinks get \
--tenant public \
--namespace default \
--name pulsar-mysql-jdbc-sink

The result shows that the parallelism is 2.

{
  "tenant": "public",
  "namespace": "default",
  "name": "pulsar-mysql-jdbc-sink",
  "className": "org.apache.pulsar.io.jdbc.JdbcAutoSchemaSink",
  "inputSpecs": {
    "pulsar-mysql-jdbc-sink-topic": {
      "isRegexPattern": false
    }
  },
  "configs": {
    "password": "jdbc",
    "jdbcUrl": "jdbc:mysql://127.0.0.1:3306/pulsar_mysql_jdbc_sink",
    "userName": "root",
    "tableName": "pulsar_mysql_jdbc_sink"
  },
  "parallelism": 2,
  "processingGuarantees": "ATLEAST_ONCE",
  "retainOrdering": false,
  "autoAck": true
}

Delete a JDBC sink

You can use the Connector Admin CLI to delete a connector and perform other operations on it.

This example deletes the pulsar-mysql-jdbc-sink sink connector.

$ bin/pulsar-admin sinks delete \
--tenant public \
--namespace default \
--name pulsar-mysql-jdbc-sink

tip

For more information about pulsar-admin sinks delete options, see here.

The sink connector has been deleted successfully if the following message appears.

"Deleted successfully"

This example double-checks the status of the sink connector.

$ bin/pulsar-admin sinks get \
--tenant public \
--namespace default \
--name pulsar-mysql-jdbc-sink

The results shows that the sink connector does not exist.

HTTP 404 Not Found

Reason: Sink pulsar-mysql-jdbc-sink doesn't exist