Bug report

What Debezium connector do you use and what version?

as400 ibmi connector 2.7.0-SNAPSHOT

What is the connector configuration?

{
  "name": "schema",
  "config": {
    "connector.class": "io.debezium.connector.db2as400.As400RpcConnector",
    "tasks.max": "1",
    "database.hostname": "hostname",
    "database.dbname": "dbname",
    "port": "",
    "database.user": "username",
    "database.password": "password",
    "database.from_ccsid": 37,
    "database.to_ccsid": 285,
    "database.secure": false,
    "database.schema": "schema",
    "poll.interval.ms": 2000,
    "snapshot.mode": "initial",
    "table.include.list": "schema.table1",
    "transforms": "unwrap,schemarename",
    "transforms.schemarename.type": "com.fnz.kakfa.smt.RepackageJavaFriendlySchemaRenamer",
    "transforms.schemarename.package": "com.fnz.debezium.schema",
    "transforms.unwrap.type": "io.debezium.transforms.ExtractNewRecordState",
    "transforms.unwrap.drop.tombstones": "false",
    "transforms.unwrap.delete.handling.mode": "rewrite",
    "key.converter.schema.registry.url": "http://schema-registry:8081",
    "value.converter.schema.registry.url": "http://schema-registry:8081",
    "key.converter": "io.confluent.connect.avro.AvroConverter",
    "value.converter": "io.confluent.connect.avro.AvroConverter",
    "snapshot.max.threads": 4,
    "topic.creation.default.cleanup.policy": "compact",
    "topic.creation.default.retention.ms": -1,
    "topic.creation.default.replication.factor": 1,
    "topic.creation.default.partitions": 1,
    "field.name.adjustment.mode": "avro",
    "topic.prefix": "databasehostname."
  }
{color:#cccccc}}

What is the captured database version and mode of depoyment?

GCP

What behaviour do you expect?

to be able to configure database connector

What behaviour do you see?

config parameter not prefixed with "dataase." in config and if specified as per code don't get passed to the database connector

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

yes

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

yes

How to reproduce the issue using our tutorial deployment?

configure database parameters such as

`socket timeout`

`thread used`

`keep alive`

`from_ccsid`

`to_ccsid`

`secure`

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

database configuration options are correctly represended in code

Implementation ideas (optional)

see PR to be attached once issue raised