-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
-
False
Bug report
For bug reports, provide this information, please:
What Debezium connector do you use and what version?
Debezium Informix Connector, version 3.2.3.Final
What is the connector configuration?
{
"connector.class": "io.debezium.connector.informix.InformixConnector",
"errors.log.include.messages": "true",
"topic.creation.default.partitions": "1",
"value.converter.schema.registry.subject.name.strategy": "io.confluent.kafka.serializers.subject.TopicNameStrategy",
"key.converter.schema.registry.subject.name.strategy": "io.confluent.kafka.serializers.subject.TopicNameStrategy",
"transforms": "unwrap",
"errors.deadletterqueue.context.headers.enable": "true",
"transforms.unwrap.drop.tombstones": "false",
"topic.creation.default.replication.factor": "3",
"errors.deadletterqueue.topic.replication.factor": "3",
"transforms.unwrap.type": "io.debezium.transforms.ExtractNewRecordState",
"errors.log.enable": "true",
"key.converter": "io.confluent.connect.avro.AvroConverter",
"database.user": "*****",
"database.dbname": "cards_1952",
"topic.creation.default.compression.type": "lz4",
"column.skip.list": "cards_1952.mcp.ach_accounts.ivr_ach_act_nick,cards_1952.mcp.alert_executed.alert_msg,cards_1952.mcp.alert_executed.alert_template,cards_1952.mcp.alert_executed.alert_data,cards_1952.mcp.alert_executed.description,cards_1952.mcp.campaign_insts.ivr_message,cards_1952.mcp.campaign_insts.push_message,cards_1952.mcp.maa_sent_msg_log.message,cards_1952.mcp.merchants.merchant_image,cards_1952.mcp.stake_holders.stake_holder_logo,cards_1952.mcp.stake_holders.stake_holder_thumbnail,cards_1952.mcp.file_store_binary.file_data,cards_1952.mcp.push_notify_comm_logs.req_payload,cards_1952.mcp.web_activity_log.request_parameters",
"schema.history.internal.kafka.bootstrap.servers": "10.11.57.201:9092, 10.11.57.203:9092, 10.11.57.202:9092",
"value.converter.schema.registry.url": "http://10.11.57.201:8081",
"schema.history.internal.kafka.topic.replication.factor": "3",
"errors.max.retries": "-1",
"errors.deadletterqueue.topic.name": "informix-gpdb-source-errors",
"database.password": "******",
"name": "source_19_ach_lodbat_details",
"errors.tolerance": "none",
"skipped.operations": "d",
"pk.mode": "kafka",
"snapshot.mode": "schema_only",
"max.queue.size": "100000",
"tasks.max": "1",
"retriable.restart.connector.wait.ms": "60000",
"database.connection.retry.interval.ms": "1000",
"schema.history.internal.store.only.captured.tables.ddl": "true",
"schema.history.internal.store.only.captured.databases.ddl": "true",
"tombstones.on.delete": "true",
"topic.prefix": "inst_kafka_net_41",
"decimal.handling.mode": "double",
"schema.history.internal.kafka.topic": "cards_1952_schema-history-ach_lodbat_details",
"connection.pool.max.size": "50",
"value.converter": "io.confluent.connect.avro.AvroConverter",
"topic.creation.default.cleanup.policy": "compact",
"time.precision.mode": "connect",
"database.server.name": "inst_kafka_net_41",
"snapshot.isolation.mode": "read_committed",
"topic.creation.default.retention.ms": "604800000",
"database.port": "9260",
"schema.history.internal.kafka.recovery.poll.interval.ms": "30000",
"offset.flush.interval.ms": "10000",
"database.hostname": "10.11.56.182",
"database.connection.retries": "5",
"table.include.list": "cards_1952.mcp.ach_lodbat_details,cards_1952.mcp.cdc_signal_heartbeat",
"key.converter.schema.registry.url": "http://10.11.57.201:8081"
}
What is the captured database version and mode of deployment?
- Informix 14.10 (on-premises)
- Kafka Connect running on Confluent Platform 7.x
- Deployment: distributed worker mode
What behavior do you expect?
When openlineage.enable=false (or not configured), the connector should not attempt to use or initialize DebeziumOpenLineageEmitter. Stopping or restarting a connector should happen cleanly without errors.
What behavior do you see?
java.lang.IllegalStateException: DebeziumOpenLineageEmitter not initialized
at io.debezium.pipeline.source.snapshot.incremental.AbstractIncrementalSnapshotChangeEventSource.close(AbstractIncrementalSnapshotChangeEventSource.java:...)
...
Call init() first.
- No OpenLineage configuration is present in the connector JSON.
- This results in noisy logs and can trigger false alarms in monitoring.
Do you see the same behaviour using the latest released Debezium version?
(Ideally, also verify with latest Alpha/Beta/CR version)
Yes, this is reproducible in 3.2.3.Final.
(Not yet tested with the latest Alpha/Beta/CR release).
Do you have the connector logs, ideally from start till finish?
(You might be asked later to provide DEBUG/TRACE level log)
Yes, logs can be provided on request (the error is consistently visible on shutdown/restart).
How to reproduce the issue using our tutorial deployment?
- Deploy Debezium Informix connector with version 3.2.3.Final.
- Do not configure OpenLineage (leave defaults).
- Start the connector.
- Stop or restart the connector.
- Observe the log output — the error regarding DebeziumOpenLineageEmitter not initialized appears.
