Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]Capture changes made by connector user & document that SYS/SYSTEM changes are not captured #7909

Closed
2 tasks done
e-mhui opened this issue Apr 24, 2023 · 0 comments · Fixed by #7917
Closed
2 tasks done
Assignees
Labels
type/bug Something is wrong
Milestone

Comments

@e-mhui
Copy link
Contributor

e-mhui commented Apr 24, 2023

What happened

Table column not recognized by DML parser after ALTER.

The error message is as follows:

Caused by: io.debezium.connector.oracle.logminer.parser.DmlParserException: Failed to parse insert DML: 'insert into "JYDB"."FR_TEST"("ID","NAME","TEL","REC_ID","ADDRE") values ('10','test','1852352343','abcd','tttt');'
at io.debezium.connector.oracle.logminer.parser.LogMinerDmlParser.parseInsert(LogMinerDmlParser.java:111)
at io.debezium.connector.oracle.logminer.parser.LogMinerDmlParser.parse(LogMinerDmlParser.java:75)
at io.debezium.connector.oracle.logminer.LogMinerQueryResultProcessor.parse(LogMinerQueryResultProcessor.java:387)
... 10 more
Caused by: java.lang.ArrayIndexOutOfBoundsException: Index 4 out of bounds for length 4
at io.debezium.connector.oracle.logminer.parser.LogMinerDmlParser.parseColumnListClause(LogMinerDmlParser.java:236)

What you expected to happen

Capture changes made by connector user changes are captured

How to reproduce

Table column not recognized by DML parser after ALTER.

Environment

No response

InLong version

master

InLong Component

InLong Sort

Are you willing to submit PR?

  • Yes, I am willing to submit a PR!

Code of Conduct

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Something is wrong
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants