-
Bug
-
Resolution: Done
-
Major
-
3.0.0.Alpha2
-
None
-
False
-
None
-
False
Bug report
For bug reports, provide this information, please:
What Debezium connector do you use and what version?
2.7.0
What is the connector configuration?
{
"connector.class" : "io.debezium.connector.db2as400.As400RpcConnector",
"name" : "<connector-name>",
"sanitize.field.names" : "true",
"tasks.max" : "1",
"database.hostname" : "<server>",
"database.user" : "<user>",
"database.password" : "<password>",
"database.port" : "8471",
"database.dbname" : "<schema>",
"database.schema" : "<schema>",
"snapshot.mode" : "schema_only",
"secure" : false,
"poll.interval.ms" : "5000",
"table.include.list" : "<schema>.<table>",
"snapshot.mode" : "schema_only",
"key.converter.schema.registry.url": "http://localhost:8081",
"value.converter.schema.registry.url": "http://localhost:8081",
"key.converter" : "io.confluent.connect.avro.AvroConverter",
"value.converter" : "io.confluent.connect.avro.AvroConverter",
"socket.timeout" : "300000",
"keep.alive" : "false",
"topic.prefix" : "test.cdc.db2",
"topic.creation.default.partitions" : 3,
"topic.creation.default.replication.factor" : 1,
"topic.creation.default.cleanup.policy" : "delete,compact",
}
What is the captured database version and mode of deployment?
on-premises
What behavior do you expect?
Connector should snapshot the table schema and then start streaming events to Kafka.
What behavior do you see?
Connector crashes when schema_only config is used
Do you see the same behaviour using the latest released Debezium version?
yes
Do you have the connector logs, ideally from start till finish?
attached
