Bug report

What Debezium connector do you use and what version?

ibmi as400 connector

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."
  }

What is the captured database version and mode of depoyment?

gcp

What behaviour do you expect?

all journal entries to be captured

What behaviour do you see?

the first entry in the next block is skipped

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

yes

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

NA

How to reproduce the issue using our tutorial deployment?

Monitor changes and with an otherwise inactive database

The first journal entry will be skipped when making one change - this is often the before entry

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

Normal running

Implementation ideas (optional)

PR to be submitted after bug raised