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

Bug report

For bug reports, provide this information, please:

What Debezium connector do you use and what version?

JDBC Sink (2.7.1)

What is the connector configuration?

{
"name": "jdbc-autherr1",
"config":

{ "connector.class": "io.debezium.connector.jdbc.JdbcSinkConnector", "tasks.max": "1", "connection.url": "jdbc:postgresql://postgres:5432/dwmsdata", "connection.username": "postgresuser", "connection.password": "postgrespw", "delete.enabled": "false", "insert.mode": "upsert", "schema.evolution": "basic", "primary.key.mode": "record_value", "primary.key.fields": "MSG_TYPE,USAGE_TYPE,TRIGGER_TYPE", "topics.regex": "oracle-dwmsdata.DWMS_DATA.WS_MESSAGE_TYPE", "quote.identifiers": "true", "transforms": "route", "transforms.route.type": "org.apache.kafka.connect.transforms.RegexRouter", "transforms.route.regex": "([^.]+)\\.([^.]+)\\.([^.]+)", "transforms.route.replacement": "dwms_data.safe_$3" }

}

What is the captured database version and mode of deployment?

oracle database 19c (SE)

 

What behavior do you expect?

 

The configuration works for a single table with three primary keys. However, even though I use "insert.mode": "upsert", updating a record still results in it being added as a new record in destination database(postgres).

What behavior do you see?

<Your answer>

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

(Ideally, also verify with latest Alpha/Beta/CR version)

<Your answer>

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?

<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>