-
Bug
-
Resolution: Not a Bug
-
Major
-
None
-
2.1.2.Final
-
False
-
None
-
False
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?
Db2 Db2- 2.1.2 Connector version (debezium-connector-db2-2.1.2.Final-plugin.tar.gz)
What is the connector configuration?
connector.class: "" database.hostname: "" database.port: "" database.dbname: "" database.user: "" database.password: database.server.name: "" table.include.list: "" schema.history.internal.kafka.topic: "schemahistory.test" schema.history.internal.kafka.bootstrap.servers: topic.creation.default.replication.factor: 3 offsets.topic.replication.factor: 3 group.initial.rebalance.delay.ms: 3 key.converter: "org.apache.kafka.connect.json.JsonConverter" key.converter.schemas.enable: "false" topic.prefix: snapshot.mode: "initial" time.precision.mode: "connect" include.schema.changes: "false" topic.creation.default.partitions: 3 value.converter: "org.apache.kafka.connect.json.JsonConverter" value.converter.schemas.enable: "false" decimal.handling.mode: "string" tombstones.on.delete: "false" database.history.consumer.security.protocol: "SASL_SSL" schema.history.internal.consumer.security.protocol: "SASL_SSL" schema.history.internal.consumer.ssl.endpoint.identification.algorithm: "https" schema.history.internal.consumer.sasl.mechanism: "PLAIN"
What is the captured database version and mode of depoyment?
(E.g. on-premises, with a specific cloud provider, etc.)
ASNCDC capture for DB2 and AWS Kubernetes deployment
What behaviour do you expect?
Since there is no change in Schema of the table, it should read captured data normally
What behaviour do you see?
Even-though there has not been any changes to the Schema of the table, it is throwing below error :
org.apache.kafka.connect.errors.ConnectException: Data row is smaller than a column index, internal schema representation is probably out of sync with real database schema
Do you see the same behaviour using the latest relesead Debezium version?
(Ideally, also verify with latest Alpha/Beta/CR version)
havent tried
Do you have the connector logs, ideally from start till finish?
(You might be asked later to provide DEBUG/TRACE level log)
INFO
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>