-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
None
-
False
-
Important
In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.
Bug report
io.debezium.text.ParsingException: DDL statement couldn't be parsed. Please open a Jira issue with the statement
while iam using property :database.history.internal.skip.unparseable.ddl=true
What Debezium connector do you use and what version?
oracle 1.9
What is the connector configuration?
database.history.internal.skip.unparseable.ddl=true
What is the captured database version and mode of depoyment?
(E.g. on-premises, with a specific cloud provider, etc.)
oracle 19c enterprise
What behaviour do you expect?
<Your answer>skip unparesable ddl
What behaviour do you see?
io.debezium.text.ParsingException: DDL statement couldn't be parsed. Please open a Jira issue with the statement
Do you see the same behaviour using the latest relesead Debezium version?
(Ideally, also verify with latest Alpha/Beta/CR version)
didn't try
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>
- links to
-
RHEA-2023:120698 Red Hat build of Debezium 2.3.4 release