SingleStore Kafka Connector Properties

On this page

Configuration for the connector is controlled via the SingleStore Kafka Connector Sink configuration properties.

Confluent users will configure these properties via the Confluent UI.

The properties listed below show the SingleStore-specific properties. For a complete list of properties refer to the Apache Kafka documentation.

SingleStore Kafka Connector Sink Configuration Properties

Property	Description	Default
`connection.ddlEndpoint` (required)	Hostname or IP address of the SingleStore Master Aggregator in the `host[:port]` format, where `port` is optional. For example: `master-agg.foo.internal:3308` or `master-agg.foo.internal`.
`connection.dmlEndpoints`	Hostname or IP address of the SingleStore Aggregator nodes to run queries against in the `host[:port],host[:port],…` format, where `port` is optional and multiple hosts are separated by a comma. For example: `child-agg:3308,child-agg2`.	`ddlEndpoint`
`connection.database` (required)	If set, all connections will default to using this database.	empty)
`connection.user`	SingleStore username.	root
`connection.password`	SingleStore password.	no password
`params.<name>`	Specify a specific MySQL or JDBC parameter which will be injected into the connection URI.	empty
`max.retries`	The maximum number of times to retry on errors before failing the task.	10
`retry.backoff.ms`	The time in milliseconds to wait following an error before a retry attempt is made.	3000
`tableKey.<index_type>[.name]`	Specify additional keys to add to tables created by the connector; value of this property is the comma separated list with names of the columns to apply key; <index_type> one of (PRIMARY, COLUMNSTORE, UNIQUE, SHARD, KEY).
`singlestore.loadDataCompression`	Compress data on load; one of (GZip, LZ4, Skip).	GZip
`singlestore.metadata.allow`	Allows or denies the use of an additional meta-table to save the recording results.	true
`singlestore.metadata.table`	Specify the name of the table to save Kafka transaction metadata.	`kafka_connect_transaction_metadata`
`singlestore.tableName.<topicName>=<tableName>`	Specify an explicit table name to use for the specified topic.

Example Configuration

Refer to Config example for a sample configuration.

Last modified: February 9, 2024

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

(Optional) Run the following command to view the associated signature files.
Shell
```
curl undefined
```
Download the signature file from the SingleStore release server.
- Option 1: Click the Download Signature button next to the SingleStore file.
- Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.
- Option 3: Run the following command to download the signature file.
  Shell
```
curl -O undefined
```

After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

Shell

echo -n undefined |
    cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
      --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
      --bundle undefined \
      --new-bundle-format -

Verified OK