In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

Bug report

First created the table in mysql source and then created the source and sink connector in kafka and did not delete and update the data in the table, get a error

What Debezium connector do you use and what version?

debezium-connector-mysql-3.2.0.Alpha1
debezium-connector-jdbc-3.2.0.Alpha1

What is the connector configuration?

{
  "name": "mysql-connector",
  "config":

{     "connector.class": "io.debezium.connector.mysql.MySqlConnector",     "database.hostname": "localhost",     "database.port": 3306,     "database.user": "xxxxxx",     "database.password": "xxxx@rrrrrrrrr",     "database.server.id": 1,     "database.ignore.ddl.commands": "CREATE PROCEDURE,CREATE FUNCTION,CREATE TRIGGER,CREATE EVENT,CREATE VIEW,ALTER PROCEDURE,ALTER FUNCTION,ALTER TRIGGER,ALTER EVENT,ALTER VIEW,DROP PROCEDURE,DROP FUNCTION,DROP TRIGGER,DROP EVENT,DROP VIEW",     "database.include.list": "dev_kafka",     "table.include.list": "dev_kafka.products",     "schema.history.internal.kafka.topic.acks": "all",     "schema.history.internal.kafka.topic.compression.type": "none",     "schema.history.internal.producer.override.acks": "all",     "schema.history.internal.producer.override.linger.ms": "100",     "schema.history.internal.store.only.captured.databases.ddl": "false",      "schema.history.internal.kafka.topic":"mysql5_schema_history",     "schema.history.internal.kafka.bootstrap.servers": "localhost:9092",     "snapshot.mode": "initial",     "snapshot.fetch.size": 2000,     "topic.prefix": "OMS",     "snapshot.locking.mode": "minimal",     "include.schema.changes": true,     "binlog.row.image": "FULL",     "poll.interval.ms": 500,     "max.batch.size": 20480,     "max.queue.size": 81920,     "schema.history.internal.store.only.monitored.tables.ddl": "true",     "schema.history.internal.skip.unparseable.ddl": "true",     "schema.name.adjustment.mode": "avro",     "topic.creation.default.replication.factor": 1,     "topic.creation.default.partitions": 1,     "topic.creation.default.cleanup.policy": "delete",     "topic.creation.default.retention.ms": "604800000",     "topic.creation.include": "OMS.dev_kafka.*",     "topic.creation.groups": "dev_kafka_group",     "topic.creation.dev_kafka_group.include": "OMS.dev_kafka.*",     "column.propagate.source.type": ".*",     "datatype.propagate.source.type": "geometry,json",     "table.ignore.builtin.schemas": "false",     "snapshot.include.collection.list": "dev_kafka.*",     "signal.data.collection": "dev_kafka.debezium_signal",     "signal.poll.interval.ms": "5000",     "log.connector": "DEBUG",     "log.mining.query.filter": "DEBUG",     "log.mining.transaction.retention.hours": "1"            }

}

What is the captured database version and mode of deployment?

Mysql v5.7.43 for Centos 7.6

What behavior do you expect?

Synchronize mysql table data to oracle and convert table names and column names to uppercase.

What behavior do you see?

get a error: Error transforming field names: Invalid value: null used for required field: "ID", schema type: INT32 (io.debezium.connector.jdbc.transforms.FieldNameTransformation:142)
org.apache.kafka.connect.errors.DataException: Invalid value: null used for required field: "ID", schema type: INT32

Do you see the same behaviour using the latest released Debezium version?

with latest Alpha1

Do you have the connector logs, ideally from start till finish?

(You might be asked later to provide DEBUG/TRACE level log)

<Your answer>

How to reproduce the issue using our tutorial deployment?

1. 1. sink-connector  

 "transforms": "schema-uppercase,tablename-uppercase",
    "transforms.schema-uppercase.type": "io.debezium.connector.jdbc.transforms.CollectionNameTransformation",
    "transforms.schema-uppercase.collection.naming.style": "upper_case",
    "transforms.tablename-uppercase.type": "io.debezium.connector.jdbc.transforms.FieldNameTransformation",
    "transforms.tablename-uppercase.column.naming.style": "upper_case",

Feature request or enhancement

For feature requests or enhancements, provide this information, please:

Which use case/requirement will be addressed by the proposed feature?

<Your answer>

Implementation ideas (optional)

<Your answer>