-
Bug
-
Resolution: Done
-
Major
-
2.5.1.Final
-
None
-
False
-
None
-
False
Bug report
For bug reports, provide this information, please:
What Debezium connector do you use and what version?
debezium-connector-oracle version 2.5.1.Final
What is the connector configuration?
{ "name": "source-data-types-connector", "config": { "connector.class": "io.debezium.connector.oracle.OracleConnector", "tasks.max": "1", "database.hostname": "oracle", "database.port": "1521", "database.user": "c##dbzuser", "database.password": "dbz", "database.dbname": "orclcdb", "database.pdb.name": "orclpdb1", "database.connection.adapter": "logminer", "topic.prefix": "dbz", "lob.enabled": "true", "schema.name.adjustment.mode": "avro", "table.include.list": "C##DBZUSER.SOURCE_DATA_TYPES", "include.schema.changes": "false", "schema.history.internal.kafka.bootstrap.servers" : "kafka:9092", "schema.history.internal.kafka.topic": "schema-changes.data-types", "heartbeat.interval.ms": "60000", "log.mining.strategy": "online_catalog", "log.mining.query.filter.mode": "in", "custom.metric.tags": "connector=source-data-types-connector", "key.converter": "org.apache.kafka.connect.json.JsonConverter", "key.converter.schemas.enable": "true", "value.converter": "org.apache.kafka.connect.json.JsonConverter", "value.converter.schemas.enable": "true" } }
What is the captured database version and mode of deployment?
Oracle Database 19, Docker
What behaviour do you expect?
LogMiner batch size is automatically increased within range if Oracle connector detects a lag from the current SCN.
What behaviour do you see?
LogMiner batch size remains unchanged.
Do you see the same behaviour using the latest relesead Debezium version?
Yes
Feature request or enhancement
PR: https://github.com/debezium/debezium/pull/5229
Implementation ideas (optional)
Necessary changes were lost after code refactoring (DBZ-6899).
- relates to
-
DBZ-6899 Refactor Oracle streaming metrics beans
- Closed
- links to
-
RHEA-2024:129636 Red Hat build of Debezium 2.5.4 release