Couchbase Sink Connector for Confluent Cloud

The fully-managed Couchbase Sink connector for Confluent Cloud maps and persists events from Apache Kafka® topics directly to a Couchbase database collection. The connector supports AVRO, BYTES, JSON Schema, PROTOBUF, or JSON (schemaless) data from Apache Kafka® topics. The connector ingests events from Kafka topics directly into a Couchbase database, exposing the data to services for querying, enrichment, and analytics.

Note

If you require private networking for fully-managed connectors, make sure to set up the proper networking beforehand. For more information, see Manage Networking for Confluent Cloud Connectors.

Features

The connector provides the following features:

  • At least once delivery: The connector guarantees that records are written at least once to Couchbase unless the record is intentionally discarded by a custom sink handler.

  • Database authentication: Uses password authentication.

  • Client-side field level encryption (CSFLE) support: The connector supports CSFLE for sensitive data. For more information about CSFLE setup, see the connector configuration.

  • Input data formats: The connector supports AVRO, BYTES, JSON_SR, PROTOBUF, or JSON (schemaless) input data formats. Schema Registry must be enabled to use a Schema Registry-based format (for example, AVRO, JSON_SR (JSON Schema), or PROTOBUF). For more information, see Schema Registry Enabled Environments.

  • Select sink behavior:

    • "couchbase.default.collection": Specifies the default Couchbase collection for records from Kafka topics not explicitly mapped.
    • "couchbase.topic.to.collection": Provides granular data routing by mapping specific Kafka topics to Couchbase collections.
    • "couchbase.topic.to.document.id": Enables per-topic overrides for Couchbase document ID formatting.
    • "couchbase.sink.handler": Defines how Kafka records are transformed into actions on Couchbase documents, supporting built-in and custom handlers.

    For details about all property values and definitions, see Configuration Properties.

For more information and examples to use with the Confluent Cloud API for Connect, see the Confluent Cloud API for Connect Usage Examples section.

Limitations

Be sure to review the following information.

Quick Start

Use this quick start to get up and running with the Confluent Cloud Couchbase Sink connector. The quick start provides the basics of selecting the connector and configuring it to consume data from Kafka and persist the data to a Couchbase database.

Prerequisites
  • Kafka cluster credentials. The following lists the different ways you can provide credentials.
    • Enter an existing service account resource ID.
    • Create a Confluent Cloud service account for the connector. Make sure to review the ACL entries required in the service account documentation. Some connectors have specific ACL requirements.
    • Create a Confluent Cloud API key and secret. To create a key and secret, you can use confluent api-key create or you can autogenerate the API key and secret directly in the Cloud Console when setting up the connector.

Using the Confluent Cloud Console

Step 1: Launch your Confluent Cloud cluster

To create and launch a Kafka cluster in Confluent Cloud, see Create a kafka cluster in Confluent Cloud.

Step 2: Add a connector

In the left navigation menu, click Connectors. If you already have connectors in your cluster, click + Add connector.

Step 3: Select your connector

Click the Couchbase Sink connector card.

Couchbase Sink Connector Card

Step 4: Enter the connector details

Note

  • Ensure you have all your prerequisites completed.
  • An asterisk ( * ) designates a required entry.

At the Add Couchbase DB Sink Connector screen, complete the following:

If you’ve already populated your Kafka topics, select the topics you want to connect from the Topics list.

To create a new topic, click +Add new topic.

Step 5: Check Couchbase database

After the connector is running, verify that messages are being added to your Couchbase database.

Tip

When you launch a connector, a Dead Letter Queue topic is automatically created. See View Connector Dead Letter Queue Errors in Confluent Cloud for details.

Using the Confluent CLI

Complete the following steps to set up and run the connector using the Confluent CLI.

Note

Make sure you have all your prerequisites completed.

Step 1: List the available connectors

Enter the following command to list available connectors:

confluent connect plugin list

Step 2: List the connector configuration properties

Enter the following command to show the connector configuration properties:

confluent connect plugin describe <connector-plugin-name>

The command output shows the required and optional configuration properties.

Step 3: Create the connector configuration file

Create a JSON file that contains the connector configuration properties. The following example shows the required connector properties.

{
    "connector.class": "CouchbaseSink",
    "name": "CouchbaseSinkConnector_0",
    "kafka.auth.mode": "KAFKA_API_KEY",
    "kafka.api.key": "<my-kafka-api-key",
    "kafka.api.secret": "<my-kafka-api-secret>",
    "input.data.format" : "JSON",
    "couchbase.seed.nodes": "<couchbase-node-address>",
    "couchbase.bucket": "<bucket-name>",
    "topics": "dlq-bcc-devcjd1abc",
    "couchbase.username": "<database-username>",
    "couchbase.password": "<database-password>",
    "couchbase.default.collection": "_default._default",
    "couchbase.sink.handler": "com.couchbase.connect.kafka.handler.sink.UpsertSinkHandler",
    "couchbase.remove.document.id": "false",
    "couchbase.document.expiration": "0",
    "couchbase.retry.timeout": "0",
    "couchbase.durability": "NONE",
    "couchbase.persist.to": "NONE",
    "couchbase.replicate.to": "NONE",
    "tasks.max": "1"
}

Note the following property definitions:

  • "connector.class": Identifies the connector plugin name.
  • "name": Sets a name for your new connector.

  • "kafka.auth.mode": Identifies the connector authentication mode you want to use. There are two options: SERVICE_ACCOUNT or KAFKA_API_KEY (the default). To use an API key and secret, specify the configuration properties kafka.api.key and kafka.api.secret, as shown in the example configuration (above). To use a service account, specify the Resource ID in the property kafka.service.account.id=<service-account-resource-ID>. To list the available service account resource IDs, use the following command:

    confluent iam service-account list

    For example:

    confluent iam service-account list

   Id     | Resource ID |       Name        |    Description
+---------+-------------+-------------------+-------------------
   123456 | sa-l1r23m   | sa-1              | Service account 1
   789101 | sa-l4d56p   | sa-2              | Service account 2

  • "input.data.format": Sets the input Kafka record value format (data coming from the Kafka topic). Valid entires are AVRO, BYTES, JSON_SR (JSON Schema), PROTOBUF, or JSON (schemaless). You must have Confluent Cloud Schema Registry configured if using a schema-based message format (for example, AVRO, JSON_SR (JSON Schema), or PROTOBUF).

  • "couchbase.seed.nodes": A comma-separated addresses of Couchbase Server nodes. If a custom port is specified, it must be the KV port (which is normally 11210 for insecure connections, or 11207 for secure connections).

  • "couchbase.bucket": Name of the Couchbase bucket to use. This property is required unless using the experimental AnalyticsSinkHandler.

  • "couchbase.username": The name of the Couchbase user connecting to the Couchbase database.

  • "couchbase.password": The password of the Couchbase user connecting to the Couchbase database.

  • "couchbase.source.handler": The source handler determines how the Couchbase document is converted into a Kafka record. When using a custom source handler that filters out certain messages, consider also configuring couchbase.black.hole.topic property.

  • Enter the number of tasks for the connector. For more information, see Confluent Cloud connector limitations.

Note

(Optional) To enable CSFLE for data encryption, specify the following properties:

  • csfle.enabled: Flag to indicate whether the connector honors CSFLE rules.
  • sr.service.account.id: A Service Account to access the Schema Registry and associated encryption rules or keys with that schema.
  • csfle.onFailure: Configures the connector behavior (ERROR or NONE) on data decryption failure. If set to ERROR, the connector fails and writes the encrypted data in the DLQ. If set to NONE, the connector writes the encrypted data in the target system without decryption.

For more information on CSFLE setup, see Manage CSFLE for connectors.

Single Message Transforms: For more information about adding SMTs using the CLI, see Single Message Transforms (SMT) documentation.

See Configuration Properties for all property values and definitions.

Step 4: Load the properties file and create the connector

Enter the following command to load the configuration and start the connector:

confluent connect cluster create --config-file <file-name>.json

For example:

confluent connect cluster create --config-file CouchbaseSink.json

Example output:

Created connector confluent-CouchbaseSink lcc-ix4dl

Step 5: Check the connector status

Enter the following command to check the connector status:

confluent connect cluster list

Example output:

ID          |            Name         | Status  | Type
+-----------+-------------------------+---------+------+
lcc-ix4dl   | confluent-CouchbaseSink | RUNNING | sink

Step 6: Check Couchbase

After the connector is running, verify that records are populating your Couchbase database.

Tip

When you launch a connector, a Dead Letter Queue topic is automatically created. See View Connector Dead Letter Queue Errors in Confluent Cloud for details.

Configuration Properties

Use the following configuration properties with the fully-managed connector. For self-managed connector property definitions and other details, see the connector docs in Self-managed connectors for Confluent Platform.

How should we connect to your data?

name

Sets a name for your connector.

  • Type: string
  • Valid Values: A string at most 64 characters long
  • Importance: high

Schema Config

schema.context.name

Add a schema context name. A schema context represents an independent scope in Schema Registry. It is a separate sub-schema tied to topics in different Kafka clusters that share the same Schema Registry instance. If not used, the connector uses the default schema configured for Schema Registry in your Confluent Cloud environment.

  • Type: string
  • Default: default
  • Importance: medium

Kafka Cluster credentials

kafka.auth.mode

Kafka Authentication mode. It can be one of KAFKA_API_KEY or SERVICE_ACCOUNT. It defaults to KAFKA_API_KEY mode.

  • Type: string
  • Default: KAFKA_API_KEY
  • Valid Values: KAFKA_API_KEY, SERVICE_ACCOUNT
  • Importance: high
kafka.api.key

Kafka API Key. Required when kafka.auth.mode==KAFKA_API_KEY.

  • Type: password
  • Importance: high
kafka.service.account.id

The Service Account that will be used to generate the API keys to communicate with Kafka Cluster.

  • Type: string
  • Importance: high
kafka.api.secret

Secret associated with Kafka API key. Required when kafka.auth.mode==KAFKA_API_KEY.

  • Type: password
  • Importance: high

Connection

couchbase.seed.nodes

Addresses of Couchbase Server nodes, delimited by commas. If a custom port is specified, it must be the KV port (which is normally 11210 for insecure connections, or 11207 for secure connections).

  • Type: string
  • Importance: high
couchbase.username

Name of the Couchbase user to authenticate as.

  • Type: string
  • Importance: high
couchbase.password

Password of the Couchbase user.

  • Type: password
  • Importance: high
couchbase.bucket

Name of the Couchbase bucket to use. This property is required unless using the experimental AnalyticsSinkHandler.

  • Type: string
  • Default: “”
  • Importance: high

Sink Behavior

couchbase.default.collection

Qualified name (scope.collection or bucket.scope.collection) of the destination collection for messages from topics that don’t have an entry in the couchbase.topic.to.collection map. If the bucket component contains a dot, escape it by enclosing it in backticks. If the bucket component is omitted, it defaults to the value of the couchbase.bucket property.

  • Type: string
  • Default: _default._default
  • Importance: medium
couchbase.topic.to.collection

A map from Kafka topic to Couchbase collection. Topic and collection are joined by an equals sign. Map entries are delimited by commas. A collection name is of the form bucket.scope.collection or scope.collection. If the bucket component is omitted, it defaults to the value of the couchbase.bucket property. If the bucket component contains a dot, escape it by enclosing it in backticks. For example, if you want to write messages from topic “topic1” to collection “scope-a.invoices” in the default bucket, and messages from topic “topic2” to collection “scope-a.widgets” in bucket “other-bucket” you would write: “topic1=scope-a.invoices,topic2=other-bucket.scope-a.widgets”. Defaults to an empty map, with all documents going to the collection specified by couchbase.default.collection.

  • Type: string
  • Default: “”
  • Importance: medium
couchbase.topic.to.document.id

A map of per-topic overrides for the couchbase.document.id configuration property. Topic and document ID format are joined by an equals sign. Map entries are delimited by commas. For example, if documents from topic “topic1” should be assigned document IDs that match their “id” field, and documents from topic “topic2” should be assigned documents IDs that match their “identifier” field, you would write: “topic1=${/id},topic2=${/identifier}”. Defaults to an empty map, which means the value of the couchbase.document.id configuration property is applied to documents from all topics.

  • Type: string
  • Default: “”
  • Importance: medium
couchbase.sink.handler

The fully-qualified class name of the sink handler to use. The sink handler determines how the Kafka record is translated into actions on Couchbase documents. The built-in handlers are: com.couchbase.connect.kafka.handler.sink.UpsertSinkHandler, com.couchbase.connect.kafka.handler.sink.N1qlSinkHandler, and com.couchbase.connect.kafka.handler.sink.SubDocumentSinkHandler. You can customize the sink connector’s behavior by implementing your own SinkHandler.

  • Type: string
  • Default: com.couchbase.connect.kafka.handler.sink.UpsertSinkHandler
  • Valid Values: com.couchbase.connect.kafka.handler.sink.AnalyticsSinkHandler, com.couchbase.connect.kafka.handler.sink.N1qlSinkHandler, com.couchbase.connect.kafka.handler.sink.SubDocumentSinkHandler, com.couchbase.connect.kafka.handler.sink.UpsertSinkHandler
  • Importance: medium
couchbase.document.id

Format string to use for the Couchbase document ID (overriding the message key). May refer to document fields via placeholders like ${/path/to/field}

  • Type: string
  • Default: “”
  • Importance: medium
couchbase.remove.document.id

Whether to remove the ID identified by ‘couchbase.documentId’ from the document before storing in Couchbase.

  • Type: boolean
  • Default: false
  • Importance: medium
couchbase.document.expiration

Document expiration time specified as an integer followed by a time unit (s = seconds, m = minutes, h = hours, d = days). For example, to have documents expire after 30 minutes, set this value to “30m”. A value of “0” (the default) means documents never expire.

  • Type: string
  • Default: 0
  • Valid Values: Must match the regex ^0$|^[1-9]\d*(ms|s|m|h|d)$
  • Importance: medium
couchbase.retry.timeout

Retry failed writes to Couchbase until this deadline is reached. If time runs out, the connector terminates. A value of 0 (the default) means the connector will terminate immediately when a write fails. This retry timeout is distinct from the KV timeout (which you can set via couchbase.env.*). The KV timeout affects an individual write attempt, while the retry timeout spans multiple attempts and makes the connector resilient to more kinds of transient failures. Try not to confuse this with the Kafka Connect framework’s built-in errors.retry.timeout config property, which applies only to failures occurring before the framework delivers the record to the Couchbase connector.

  • Type: string
  • Default: 0
  • Valid Values: Must match the regex ^0$|^[1-9]\d*(ms|s|m|h|d)$
  • Importance: medium

Durability

couchbase.durability

The preferred way to specify an enhanced durability requirement when using Couchbase Server 6.5 or later. The default value of NONE means a write is considered successful as soon as it reaches the memory of the active node. If you set this to anything other than NONE, then you must not set couchbase.persist.to or couchbase.replicate.to.

  • Type: string
  • Default: NONE
  • Valid Values: MAJORITY, MAJORITY_AND_PERSIST_TO_ACTIVE, NONE, PERSIST_TO_MAJORITY
  • Importance: medium
couchbase.persist.to

For Couchbase Server versions prior to 6.5, this is how you require the connector to verify a write is persisted to disk on a certain number of replicas before considering the write successful. If you’re using Couchbase Server 6.5 or later, we recommend using the couchbase.durability property instead.

  • Type: string
  • Default: NONE
  • Valid Values: ACTIVE, FOUR, NONE, ONE, THREE, TWO
  • Importance: medium
couchbase.replicate.to

For Couchbase Server versions prior to 6.5, this is how you require the connector to verify a write has reached the memory of a certain number of replicas before considering the write successful. If you’re using Couchbase Server 6.5 or later, we recommend using the couchbase.durability property instead.

  • Type: string
  • Default: NONE
  • Valid Values: NONE, ONE, THREE, TWO
  • Importance: medium

N1ql Sink Handler

couchbase.n1ql.operation

The type of update to use when couchbase.sink.handler is set to com.couchbase.connect.kafka.handler.sink.N1qlSinkHandler. This property is specific to N1qlSinkHandler.

  • Type: string
  • Default: UPDATE
  • Valid Values: UPDATE, UPDATE_WHERE
  • Importance: medium
couchbase.n1ql.where.fields

When using the UPDATE_WHERE operation, this is the list of document fields that must match the Kafka message in order for the document to be updated with the remaining message fields. To match against a literal value instead of a message field, use a colon to delimit the document field name and the target value. For example, “type:widget,color” matches documents whose ‘type’ field is ‘widget’ and whose ‘color’ field matches the ‘color’ field of the Kafka message. This property is specific to N1qlSinkHandler.

  • Type: string
  • Default: “”
  • Importance: medium
couchbase.n1ql.create.document

Controls whether to create the document if it does not exist. This property is specific to N1qlSinkHandler.

  • Type: boolean
  • Default: true
  • Importance: medium

Sub Document Sink Handler

couchbase.subdocument.path

JSON Pointer to the property of the Kafka message whose value is the subdocument path to use when modifying the Couchbase document. This property is specific to SubDocumentSinkHandler.

  • Type: string
  • Default: “”
  • Importance: medium
couchbase.subdocument.operation

Setting to indicate the type of update to a sub-document. This property is specific to SubDocumentSinkHandler.

  • Type: string
  • Default: UPSERT
  • Valid Values: ARRAY_APPEND, ARRAY_PREPEND, UPSERT
  • Importance: medium
couchbase.subdocument.create.path

Whether to add the parent paths if they are missing in the document. This property is specific to SubDocumentSinkHandler.

  • Type: boolean
  • Default: true
  • Importance: medium
couchbase.subdocument.create.document

This property controls whether to create the document if it does not exist. This property is specific to SubDocumentSinkHandler.

  • Type: boolean
  • Default: true
  • Importance: medium

Analytics Sink Handler

couchbase.analytics.max.records.in.batch

Every Batch consists of an UPSERT or a DELETE statement, based on mutations. This property determines the maximum number of records in the UPSERT or DELETE statement in the batch. Users can configure this parameter based on the capacity of their analytics cluster. This property is specific to AnalyticsSinkHandler. UNCOMMITTED; this feature may change in a patch release without notice. Since: 4.1.14

  • Type: int
  • Default: 100
  • Importance: medium
couchbase.analytics.max.size.in.batch

Every Batch consists of an UPSERT or a DELETE statement, based on mutations. This property defines the max size of all docs in bytes in an UPSERT statement in a batch. Users can configure this parameter based on the capacity of their analytics cluster. This property is specific to AnalyticsSinkHandler. UNCOMMITTED; this feature may change in a patch release without notice. Since: 4.2.0

  • Type: string
  • Default: 5m
  • Valid Values: Must match the regex ^[1-9]\d*(b|k|m|g)$
  • Importance: medium
couchbase.analytics.query.timeout

This property determines the time period after which client cancels the Query request for Analytics. This property is specific to AnalyticsSinkHandler. UNCOMMITTED; this feature may change in a patch release without notice. Since: 4.2.0

  • Type: string
  • Default: 5m
  • Valid Values: Must match the regex ^[1-9]\d*(ms|s|m|h|d)$
  • Importance: medium

Additional Configs

consumer.override.auto.offset.reset

Defines the behavior of the consumer when there is no committed position (which occurs when the group is first initialized) or when an offset is out of range. You can choose either to reset the position to the “earliest” offset or the “latest” offset (the default). You can also select “none” if you would rather set the initial offset yourself and you are willing to handle out of range errors manually. More details: https://docs.confluent.io/platform/current/installation/configuration/consumer-configs.html#auto-offset-reset

  • Type: string
  • Importance: low
consumer.override.isolation.level

Controls how to read messages written transactionally. If set to read_committed, consumer.poll() will only return transactional messages which have been committed. If set to read_uncommitted (the default), consumer.poll() will return all messages, even transactional messages which have been aborted. Non-transactional messages will be returned unconditionally in either mode. More details: https://docs.confluent.io/platform/current/installation/configuration/consumer-configs.html#isolation-level

  • Type: string
  • Importance: low
header.converter

The converter class for the headers. This is used to serialize and deserialize the headers of the messages.

  • Type: string
  • Importance: low
value.converter.allow.optional.map.keys

Allow optional string map key when converting from Connect Schema to Avro Schema. Applicable for Avro Converters.

  • Type: boolean
  • Importance: low
value.converter.auto.register.schemas

Specify if the Serializer should attempt to register the Schema.

  • Type: boolean
  • Importance: low
value.converter.connect.meta.data

Allow the Connect converter to add its metadata to the output schema. Applicable for Avro Converters.

  • Type: boolean
  • Importance: low
value.converter.enhanced.avro.schema.support

Enable enhanced schema support to preserve package information and Enums. Applicable for Avro Converters.

  • Type: boolean
  • Importance: low
value.converter.enhanced.protobuf.schema.support

Enable enhanced schema support to preserve package information. Applicable for Protobuf Converters.

  • Type: boolean
  • Importance: low
value.converter.flatten.unions

Whether to flatten unions (oneofs). Applicable for Protobuf Converters.

  • Type: boolean
  • Importance: low
value.converter.generate.index.for.unions

Whether to generate an index suffix for unions. Applicable for Protobuf Converters.

  • Type: boolean
  • Importance: low
value.converter.generate.struct.for.nulls

Whether to generate a struct variable for null values. Applicable for Protobuf Converters.

  • Type: boolean
  • Importance: low
value.converter.int.for.enums

Whether to represent enums as integers. Applicable for Protobuf Converters.

  • Type: boolean
  • Importance: low
value.converter.latest.compatibility.strict

Verify latest subject version is backward compatible when use.latest.version is true.

  • Type: boolean
  • Importance: low
value.converter.object.additional.properties

Whether to allow additional properties for object schemas. Applicable for JSON_SR Converters.

  • Type: boolean
  • Importance: low
value.converter.optional.for.nullables

Whether nullable fields should be specified with an optional label. Applicable for Protobuf Converters.

  • Type: boolean
  • Importance: low
value.converter.optional.for.proto2

Whether proto2 optionals are supported. Applicable for Protobuf Converters.

  • Type: boolean
  • Importance: low
value.converter.scrub.invalid.names

Whether to scrub invalid names by replacing invalid characters with valid characters. Applicable for Avro and Protobuf Converters.

  • Type: boolean
  • Importance: low
value.converter.use.latest.version

Use latest version of schema in subject for serialization when auto.register.schemas is false.

  • Type: boolean
  • Importance: low
value.converter.use.optional.for.nonrequired

Whether to set non-required properties to be optional. Applicable for JSON_SR Converters.

  • Type: boolean
  • Importance: low
value.converter.wrapper.for.nullables

Whether nullable fields should use primitive wrapper messages. Applicable for Protobuf Converters.

  • Type: boolean
  • Importance: low
value.converter.wrapper.for.raw.primitives

Whether a wrapper message should be interpreted as a raw primitive at root level. Applicable for Protobuf Converters.

  • Type: boolean
  • Importance: low
errors.tolerance

Use this property if you would like to configure the connector’s error handling behavior. WARNING: This property should be used with CAUTION for SOURCE CONNECTORS as it may lead to dataloss. If you set this property to ‘all’, the connector will not fail on errant records, but will instead log them (and send to DLQ for Sink Connectors) and continue processing. If you set this property to ‘none’, the connector task will fail on errant records.

  • Type: string
  • Default: all
  • Importance: low
key.converter.key.subject.name.strategy

How to construct the subject name for key schema registration.

  • Type: string
  • Default: TopicNameStrategy
  • Importance: low
value.converter.decimal.format

Specify the JSON/JSON_SR serialization format for Connect DECIMAL logical type values with two allowed literals:

BASE64 to serialize DECIMAL logical types as base64 encoded binary data and

NUMERIC to serialize Connect DECIMAL logical type values in JSON/JSON_SR as a number representing the decimal value.

  • Type: string
  • Default: BASE64
  • Importance: low
value.converter.flatten.singleton.unions

Whether to flatten singleton unions. Applicable for Avro and JSON_SR Converters.

  • Type: boolean
  • Default: false
  • Importance: low
value.converter.ignore.default.for.nullables

When set to true, this property ensures that the corresponding record in Kafka is NULL, instead of showing the default column value. Applicable for AVRO,PROTOBUF and JSON_SR Converters.

  • Type: boolean
  • Default: false
  • Importance: low
value.converter.reference.subject.name.strategy

Set the subject reference name strategy for value. Valid entries are DefaultReferenceSubjectNameStrategy or QualifiedReferenceSubjectNameStrategy. Note that the subject reference name strategy can be selected only for PROTOBUF format with the default strategy being DefaultReferenceSubjectNameStrategy.

  • Type: string
  • Default: DefaultReferenceSubjectNameStrategy
  • Importance: low
value.converter.replace.null.with.default

Whether to replace fields that have a default value and that are null to the default value. When set to true, the default value is used, otherwise null is used. Applicable for JSON Converter.

  • Type: boolean
  • Default: true
  • Importance: low
value.converter.schemas.enable

Include schemas within each of the serialized values. Input messages must contain schema and payload fields and may not contain additional fields. For plain JSON data, set this to false. Applicable for JSON Converter.

  • Type: boolean
  • Default: false
  • Importance: low
value.converter.value.subject.name.strategy

Determines how to construct the subject name under which the value schema is registered with Schema Registry.

  • Type: string
  • Default: TopicNameStrategy
  • Importance: low

Consumer configuration

max.poll.interval.ms

The maximum delay between subsequent consume requests to Kafka. This configuration property may be used to improve the performance of the connector, if the connector cannot send records to the sink system. Defaults to 300000 milliseconds (5 minutes).

  • Type: long
  • Default: 300000 (5 minutes)
  • Valid Values: [60000,…,1800000] for non-dedicated clusters and [60000,…] for dedicated clusters
  • Importance: low
max.poll.records

The maximum number of records to consume from Kafka in a single request. This configuration property may be used to improve the performance of the connector, if the connector cannot send records to the sink system. Defaults to 500 records.

  • Type: long
  • Default: 500
  • Valid Values: [1,…,500] for non-dedicated clusters and [1,…] for dedicated clusters
  • Importance: low

Input messages

input.data.format

Sets the input Kafka record value format. Valid entries are AVRO, JSON_SR, PROTOBUF, JSON or BYTES. Note that you need to have Confluent Cloud Schema Registry configured if using a schema-based message format like AVRO, JSON_SR, and PROTOBUF.

  • Type: string
  • Default: JSON
  • Importance: high

Number of tasks for this connector

tasks.max

Maximum number of tasks for the connector.

  • Type: int
  • Valid Values: [1,…]
  • Importance: high

Which topics do you want to get data from?

topics

Identifies the topic name or a comma-separated list of topic names.

  • Type: list
  • Importance: high

Auto-restart policy

auto.restart.on.user.error

Enable connector to automatically restart on user-actionable errors.

  • Type: boolean
  • Default: true
  • Importance: medium

Next Steps

For an example that shows fully-managed Confluent Cloud connectors in action with Confluent Cloud ksqlDB, see the Cloud ETL Demo. This example also shows how to use Confluent CLI to manage your resources in Confluent Cloud.

../../_images/topology.png