Limitations when using Confluent Cloud for topic and schema creation - Connect_CDC - connect_cdc_mimix_share - 6.x

Connect CDC Getting Started Guide

Product type
Software
Portfolio
Integrate
Product family
Connect
Product
Connect > Connect CDC (MIMIX Share)
Version
6.x
ft:locale
en-US
Product name
Connect CDC
ft:title
Connect CDC Getting Started Guide
Copyright
2025
First publish date
2003
ft:lastEdition
2026-05-13
ft:lastPublication
2026-05-13T20:40:47.043000
L1_Product_Gateway
Integrate
L2_Product_Segment
Data Integration
L3_Product_Brand
Precisely Connect
L4_Investment_Segment
Application Data Integration
L5_Product_Group
ADI - Connect
L6_Product_Name
Connect CDC
Important: When using the Confluent Cloud flavor of Kafka, Connect CDC cannot automatically create Kafka topics.

Connect CDC creates topics through a Kafka consumer, which relies on the Kafka broker property auto.create.topics.enable being set to true. In Confluent Cloud, this broker property is set to false by default and cannot be modified in most environments, as documented by Confluent.

Because topic creation is disabled, the Share operation cannot be used to create new topics in Confluent Cloud.

This limitation does not prevent schema registration when topics already exist. In Connect CDC, you are expected to manually create Kafka topics in Confluent Cloud. Once the topic is available, Connect CDC can automatically generate and register the schema for the selected source table during distribution, without attempting to create the topic. If a schema already exists, it can be reused; otherwise, Connect CDC can attempt to register the schema against the existing topic.

To support Confluent Cloud environments, Precisely recommends manually creating Kafka topics and schemas before configuring Connect CDC, or using an external process to generate schemas and registering them directly in Schema Registry.