Kafka Connect
- What's causing “Connector failed because of it encountered some bad records" Error using MySQL Sink Connector on Confluent Cloud
- What can cause “The connection to MySQL server timed out” Error using MySQL Source/Sink Connector on Confluent Cloud
- How to handle "failure with database connection" Error with Postgres Source and Sink connector on Confluent Cloud
- How to handle “The connector doesn't support tombstone values and therefore requires records with a non-null Struct value and non-null Struct schema” Error
- What's causing “We are having some trouble connecting to your database. Please make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port.” Error using Microsoft SQL Server Source/Sink Cloud Connector
- What's causing “The config table.format.name and topic names define a fully qualified name for the table…” Error using Microsoft SQL Server Sink Cloud Connector
- How to Troubleshoot "Found nested structure in input data. Ensure that your input events are a flat struct of primitive fields" error in Confluent Cloud UI
- How to handle "MicrosoftSqlServerSink : Unable to login" error with Microsoft SQL Server Sink connector on Confluent Cloud
- How to handle "requires records with a non-null key and non-null Struct or primitive key schema" Error using JDBC sink connector on Confluent Cloud
- What can cause Database Shutdown Error for fully managed PostgresSink/PostgresCdcSourceV2 Connectors
- What can cause "Failed to parse json in one of the source files. Please ensure that the source files are valid JSON files" error with fully managed S3 Source Connectors
- What can cause "There is an illegal character in the schema field. Please ensure the schema has valid characters in it" error with Fully managed S3 Source Connector
- What can cause "Invalid value for configuration path.format: Illegal pattern component" error with Fully managed S3 Sink connector
- What's causing “Task is being killed because it was not assigned a table nor a query to execute” Error using Microsoft SQL Server Source Cloud Connector
- What's causing "You are over the space Quota on the Mongo Server" Error using MongoDB Atlas Sink Connector
- What's causing "ORA-12514, TNS:listener does not currently know of service requested in connect descriptor" Error using Oracle CDC Source Connector
- What's causing "The connector failed because the redo log file <redo log file name> cannot be opened" Error using Oracle CDC Source Cloud Connector
- How to bypass "Could not connect to the database" Error using Oracle CDC source connector on Confluent Cloud
- What's causing "unable to connect to the database due to a connection issue" Error using PostgreSQL CDC Source V2 Connector on Confluent Cloud
- How to handle "Could not convert one or more records to a BsonDocument. Please make sure the input record values contain valid JSON when using String input format" Error in fully managed MongoDB Atlas Sink connector
- How to troubleshoot: "Failed to write mongodb documents with duplicate key. If the collection contains unique constraint...." error in fully managed MongoDB Atlas Sink connector
- What can cause "The connector is having trouble reaching the database" Error using MongoDB Atlas connector on Confluent Cloud
- What can cause "ensure that the user is authorized to open/resume change streams" Error using MongoDB Atlas Source connector
- How to resolve "The connector is not authorized to access the designated topic. Please make sure the Kafka API key has correct topic ACLs enabled" error with Fully Managed Connectors in Confluent Cloud
- What is causing Source Connectors to fail with: "The request included a message larger than the max message size the server will accept" and "The message size is larger than the value of the max.request.size configuration.”
- How to bypass "NoSuchMethodError validateOAuthMechanismAndNonNullJaasConfig" using Confluent Docker images
- What's causing "With the configured document ID strategy, all records are required to have keys, which must be either maps or structs" Message using Atlas MongoDB Sink connector
- What's causing Mongo DB Atlas Source Connector fail with "The connector failed to resume change stream, as the resume point may no longer be in the oplog. Please increase the size of your oplog and recreate the connector."