Stream PostgreSQL Data into Apache Kafka Topics



Access and stream PostgreSQL data in Apache Kafka using the CData JDBC Driver and the Kafka Connect JDBC connector.

Apache Kafka is an open-source stream processing platform that is primarily used for building real-time data pipelines and event-driven applications. When paired with the CData JDBC Driver for PostgreSQL, Kafka can work with live PostgreSQL data. This article describes how to connect, access and stream PostgreSQL data into Apache Kafka Topics and to start Confluent Control Center to help users secure, manage, and monitor the PostgreSQL data received using Kafka infrastructure in the Confluent Platform.

With built-in optimized data processing, the CData JDBC Driver offers unmatched performance for interacting with live PostgreSQL data. When you issue complex SQL queries to PostgreSQL, the driver pushes supported SQL operations, like filters and aggregations, directly to PostgreSQL and utilizes the embedded SQL engine to process unsupported operations client-side (often SQL functions and JOIN operations). Its built-in dynamic metadata querying allows you to work with and analyze PostgreSQL data using native data types.

Prerequisites

Before connecting the CData JDBC Driver for streaming PostgreSQL data in Apache Kafka Topics, install and configure the following in the client Linux-based system.

  1. Confluent Platform for Apache Kafka
  2. Confluent Hub CLI Installation
  3. Self-Managed Kafka JDBC Source Connector for Confluent Platform

Define a New JDBC Connection to PostgreSQL data

  1. Download CData JDBC Driver for PostgreSQL on a Linux-based system
  2. Follow the given instructions to create a new directory extract all the driver contents into it:
    1. Create a new directory named PostgreSQL mkdir PostgreSQL
    2. Move the downloaded driver file (.zip) into this new directory mv PostgreSQLJDBCDriver.zip PostgreSQL/
    3. Unzip the CData PostgreSQLJDBCDriver contents into this new directory unzip PostgreSQLJDBCDriver.zip
  3. Open the PostgreSQL directory and navigate to the lib folder ls cd lib/
  4. Copy the contents of the lib folder of PostgreSQL into the lib folder of Kafka Connect JDBC. Check the Kafka Connect JDBC folder contents to confirm that the cdata.jdbc.postgresql.jar file is successfully copied into the lib folder cp * ../../confluent-7.5.0/share/confluent-hub-components/confluentinc-kafka-connect-jdbc/lib/ cd ../../confluent-7.5.0/share/confluent-hub-components/confluentinc-kafka-connect-jdbc/lib/
  5. Install the CData PostgreSQL JDBC driver license using the given command, followed by your Name and Email ID java -jar cdata.jdbc.postgresql.jar -l
  6. Enter the product key or "TRIAL" (In the scenarios of license expiry, please contact our CData Support team)
  7. Start the Confluent local services using the command: confluent local services start

    This starts all the Confluent Services like Zookeeper, Kafka, Schema Registry, Kafka REST, Kafka CONNECT, ksqlDB and Control Center. You are now ready to use the CData JDBC driver for PostgreSQL to stream messages using Kafka Connect Driver into Kafka Topics on ksqlDB.

    Start the Confluent local services
  8. Create the Kafka topics manually using a POST HTTP API Request: curl --location 'server_address:8083/connectors' --header 'Content-Type: application/json' --data '{ "name": "jdbc_source_cdata_postgresql_01", "config": { "connector.class": "io.confluent.connect.jdbc.JdbcSourceConnector", "connection.url": "jdbc:postgresql:User=postgres;Password=admin;Database=postgres;Server=127.0.0.1;Port=5432;", "topic.prefix": "postgresql-01-", "mode": "bulk" } }'

    Let us understand the fields used in the HTTP POST body (shown above):

    • connector.class: Specifies the Java class of the Kafka Connect connector to be used.
    • connection.url: The JDBC connection URL to connect with PostgreSQL data.

      Built-in Connection String Designer

      For assistance in constructing the JDBC URL, use the connection string designer built into the PostgreSQL JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

      java -jar cdata.jdbc.postgresql.jar

      Fill in the connection properties and copy the connection string to the clipboard.

      To connect to PostgreSQL, set the Server, Port (the default port is 5432), and Database connection properties and set the User and Password you wish to use to authenticate to the server. If the Database property is not specified, the data provider connects to the user's default database.

      Using the built-in connection string designer to generate a JDBC URL (Salesforce is shown.)

    • topic.prefix: A prefix that will be added to the Kafka topics created by the connector. It's set to "postgresql-01-".
    • mode: Specifies the mode in which the connector operates. In this case, it's set to "bulk", which suggests that the connector is configured to perform bulk data transfer.

    This request adds all the tables/contents from PostgreSQL as Kafka Topics.

    Note: The IP Address (server) to POST the request (shown above) is the Linux Network IP Address.

  9. Run ksqlDB and list the topics. Use the commands: ksql list topics; List the Kafka Topics (BigCommerce is shown)
  10. To view the data inside the topics, type the SQL Statement: PRINT topic FROM BEGINNING;

Connecting with the Confluent Control Center

To access the Confluent Control Center user interface, ensure to run the "confluent local services" as described in the above section and type http://<server address>:9021/clusters/ on your local browser.

Connect with Confluent Control Center

Get Started Today

Download a free, 30-day trial of the CData JDBC Driver for PostgreSQL and start streaming PostgreSQL data into Apache Kafka. Reach out to our Support Team if you have any questions.

Ready to get started?

Download a free trial of the PostgreSQL Driver to get started:

 Download Now

Learn more:

PostgreSQL Icon PostgreSQL JDBC Driver

Rapidly create and deploy powerful Java applications that integrate with PostgreSQL-compatible database engines.