Bug report

What Debezium connector do you use and what version?

dbz-server 2.4.0.final

What is the connector configuration?

// 

source:
  class: io.debezium.connector.mysql.MySqlConnector
  config:
    tasks.max: 1
    offset.storage.file.filename: /debezium/data/offsets.dat
    database.history: io.debezium.relational.history.FileDatabaseHistory
    database.history.store.only.captured.tables.ddl: ture
    schema.history.internal: io.debezium.storage.file.history.FileSchemaHistory
    schema.history.internal.file.filename: /debezium/data/schema_history.dat
    topic.prefix:
    database.hostname: *
    database.port: 3306
    database.server.id: *
    database.user: *
    database.password: *
    snapshot.mode: schema_only
    snapshot.locking.mode: none
    include.schema.changes: false
    tombstones.on.delete: false
    converter.type: key,value,header
    converter.schemas.enable: false
    decimal.handling .mode: double

What is the captured database version and mode of depoyment?

mysql-5.7

What behaviour do you expect?

<Your answer>

What behaviour do you see?

<Your answer>

Do you see the same behaviour using the latest relesead 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>