![]() |
VOOZH | about |
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 API Driver for JDBC, Kafka can work with live Drift data. This article describes how to connect, access and stream Drift data into Apache Kafka Topics and to start Confluent Control Center to help users secure, manage, and monitor the Drift 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 Drift data. When you issue complex SQL queries to Drift, the driver pushes supported SQL operations, like filters and aggregations, directly to Drift 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 Drift data using native data types.
Before connecting the CData JDBC Driver for streaming Drift data in Apache Kafka Topics, install and configure the following in the client Linux-based system.
mkdir API
mv APIJDBCDriver.zip API/
unzip APIJDBCDriver.zip
ls cd lib/
cp -r /path/to/CData API Driver for JDBC/lib/* /usr/share/confluent-hub-components/confluentinc-kafka-connect-jdbc/lib/ cd /usr/share/confluent-hub-components/confluentinc-kafka-connect-jdbc/lib/
java -jar cdata.jdbc.api.jar -l
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 Drift to stream messages using Kafka Connect Driver into Kafka Topics on ksqlDB.
👁 Start the Confluent local services curl --location 'server_address:8083/connectors'
--header 'Content-Type: application/json'
--data '{
"name": "jdbc_source_cdata_api_01",
"config": {
"connector.class": "io.confluent.connect.jdbc.JdbcSourceConnector",
"connection.url": "jdbc:api:Profile=C:\profiles\Drift.apip;Authscheme=OAuth;OAuthClientId=your_client_id;OAuthClientSecret=your_client_secret;CallbackUrl=your_callback_url;",
"topic.prefix": "api-01-",
"mode": "bulk"
}
}'
Let us understand the fields used in the HTTP POST body (shown above):
For assistance in constructing the JDBC URL, use the connection string designer built into the CData API Driver for JDBC. Either double-click the JAR file or execute the jar file from the command-line.
java -jar cdata.jdbc.api.jar
Fill in the connection properties and copy the connection string to the clipboard.
Start by setting the Profile connection property to the location of the Drift Profile on disk (e.g. C:\profiles\Drift.apip). Next, set the ProfileSettings connection property to the connection string for Drift (see below).
Drift uses OAuth-based authentication.
You must first register an application here: https://dev.drift.com. Your app will be assigned a client ID and a client secret. Set these in your connection string via the OAuthClientId and OAuthClientSecret properties. More information on setting up an OAuth application can be found at https://devdocs.drift.com/docs/.
After setting the following options in the ProfileSettings connection property, you are ready to connect:
This request adds all the tables/contents from Drift as Kafka Topics.
Note: The IP Address (server) to POST the request (shown above) is the Linux Network IP Address.
ksql list topics;👁 List the Kafka Topics (BigCommerce is shown)
PRINT topic FROM BEGINNING;
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 CenterDownload a free, 30-day trial of the CData API Driver for JDBC and start streaming Drift data into Apache Kafka. Reach out to our Support Team if you have any questions.
Connect to live data from Drift with the API Driver
Connect to Drift