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

Bug report

env: debezium 3.2.0 beta2 + kafka_2.13-3.9.0
source : mysql 5.7.43-log
target : oracle 19c
mysql :
create table products (
id int auto_increment primary key,
number bigint(20),
date datetime
);
insert into products values (1,10,now());
insert into products values (2,20,now());

oracle-sink configuration:

{... "quote.identifiers": "true", "transforms": "topic-uppercase,fields-uppercase", "transforms.topic-uppercase.type": "io.debezium.connector.jdbc.transforms.CollectionNameTransformation", "transforms.topic-uppercase.collection.naming.style": "upper_case", "transforms.fields-uppercase.type": "io.debezium.connector.jdbc.transforms.FieldNameTransformation", "transforms.fields-uppercase.column.naming.style": "upper_case", ...}

The target table created automatically in Oracle still has lowercase table name "products".
Field name successfully converted to uppercase.

SQL> desc OMS."products"
Name   Type         Nullable Default  
------ ------------ -------- -------  
ID     NUMBER(10) 
NUMBER NUMBER(19)   Y 
DATE   TIMESTAMP(6) Y

No errors found in the logs.

I want to transform both table and field names to uppercase.

What Debezium connector do you use and what version?

debezium-connector-mysql-3.2.0.Beta2

debezium-connector-jdbc-3.2.0.Beta2

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?

(E.g. on-premises, with a specific cloud provider, etc.)

<Your answer>

What behavior do you expect?

Transforming table and fields names to uppercase ,  

What behavior do you see?

Transforming table names to uppercase does not work, Additional information can be found in DBZ-9017

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

Yes.

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

Yes

How to reproduce the issue using our tutorial deployment?

<Your answer>

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>