Skip to main content

Create a JDBC source connector from MySQL to Apache Kafka®

The JDBC source connector pushes data from a relational database, such as MySQL, to Apache Kafka® where can be transformed and read by multiple consumers.


Sourcing data from a database into Apache Kafka decouples the database from the set of consumers. Once the data is in Apache Kafka, multiple applications can access it without adding any additional query overhead to the source database.


See the full set of available parameters and configuration options in the connector's documentation.


To setup a JDBC source connector pointing to MySQL, you need an Aiven for Apache Kafka service with Apache Kafka Connect enabled or a dedicated Aiven for Apache Kafka Connect cluster.

Furthermore you need to collect the following information about the source MySQL database upfront:

  • MYSQL_HOST: The database hostname
  • MYSQL_PORT: The database port
  • MYSQL_USER: The database user to connect
  • MYSQL_PASSWORD: The database password for the MYSQL_USER
  • MYSQL_DATABASE_NAME: The database name
  • MYSQL_TABLES: The list of database tables to be included in Apache Kafka; the list must be in the form of table_name1,table_name2

If you're using Aiven for MySQL the above details are available in the Aiven console service Overview tab or via the dedicated avn service get command with the Aiven CLI.

Setup a MySQL JDBC source connector with Aiven CLI

The following example demonstrates how to setup an Apache Kafka JDBC source connector to a MySQL database using the Aiven CLI dedicated command.

Define a Kafka Connect configuration file

Define the connector configurations in a file (we'll refer to it with the name jdbc_source_mysql.json) with the following content:


The configuration file contains the following entries:

  • name: the connector name
  • MYSQL_HOST, MYSQL_PORT, MYSQL_DATABASE_NAME, MYSQL_USER, MYSQL_PASSWORD and MYSQL_TABLES: source database parameters collected in the prerequisite phase.
  • mode: the query mode, more information in the dedicated page; depending on the selected mode, additional configuration entries might be required.
  • topic.prefix: the prefix that will be used for topic names. The resulting topic name will be the concatenation of the topic.prefix and the schema and table name.
  • tasks.max: maximum number of tasks to execute in parallel. By default is 1, the connector can use at max 1 task for each source table defined.
  • query frequency, default 5000 milliseconds

Check out the dedicated documentation for the full list of parameters.

Create a Kafka Connect connector with Aiven CLI

To create the connector, execute the following Aiven CLI command, replacing the SERVICE_NAME with the name of the Aiven service where the connector needs to run:

avn service connector create SERVICE_NAME @jdbc_source_mysql.json

Check the connector status with the following command, replacing the SERVICE_NAME with the Aiven service and the CONNECTOR_NAME with the name of the connector defined before:

avn service connector status SERVICE_NAME CONNECTOR_NAME

Verify in the Apache Kafka target instance, the presence of the topic and the data


If you're using Aiven for Apache Kafka, topics will not be created automatically. Either create them manually following the topic.prefix.schema_name.table_name naming pattern or enable the kafka.auto_create_topics_enable advanced parameter.

Example: define a JDBC incremental connector

The example creates an incremental JDBC connector with the following properties:

  • connector name: jdbc_source_mysql_increment
  • source tables: students and exams, available in an Aiven for MySQL database
  • incremental column name: id
  • topic prefix: jdbc_source_mysql_increment.
  • maximum number of concurrent tasks: 1
  • time interval between queries: 5 seconds

The connector configuration is the following:


With the above configuration stored in a jdbc_incremental_source_mysql.json file, you can create the connector in the demo-kafka instance with:

avn service connector create demo-kafka @jdbc_incremental_source_mysql.json