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

Adhoc record is inserted like this

This is my debezium_signals table DDL.

Bug report

For bug reports, provide this information, please:

What Debezium connector do you use and what version?

Latest

What is the connector configuration?

debezium.sink.type=redis
debezium.sink.redis.batch.size=500
debezium.sink.redis.address=redis:6379
debezium.sink.redis.message.format=compact

debezium.sink.redis.memory.limit.mb=0
debezium.sink.redis.memory.threshold.percentage=85

debezium.source.database.hostname=*****rds.amazonaws.com
debezium.source.database.port=3306
debezium.source.database.user=*****
debezium.source.database.password=*********
debezium.source.database.dbname=greatlea_newweboct17
debezium.source.poll.interval.ms=300000

debezium.source.topic.prefix=ds_website_001.ingest
debezium.source.connector.class=io.debezium.connector.mysql.MySqlConnector

debezium.source.schema.whitelist=greatlea_newweboct17

debezium.source.snapshot.mode=SCHEMA_ONLY_RECOVERY
debezium.source.heartbeat.interval.ms=3000
debezium.source.signal.data.collection=greatlea_newweboct17.debezium_signals
debezium.source.database.history=io.debezium.relational.history.MemoryDatabaseHistory
debezium.source.schema.history.internal=io.debezium.relational.history.MemorySchemaHistory

debezium.source.offset.flush.interval.ms=0
debezium.source.decimal.handling.mode=string
debezium.publication.autocreate.mode=filtered
debezium.source.database.server.id=*****

debezium.source.database.server.name=debezium_3
debezium.source.offset.storage.file.filename=data/offsets_website3.dat

What is the captured database version and mode of depoyment?

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

<Your answer>

What behaviour do you expect?

I should be able to initiate adhoc snapshots for tables

What behaviour do you see?

Even though records are inserted in debezium_signals table in the source mysql db. Still adhoc snapshots are not getting trigger

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>