Uploaded image for project: 'Debezium'
  1. Debezium
  2. DBZ-3689

Table column not recognized by DML parser after ALTER

    XMLWordPrintable

Details

    • Bug
    • Resolution: Not a Bug
    • Minor
    • None
    • 1.6.0.CR1
    • oracle-connector
    • None
    • False
    • False
    • Undefined

    Description

      The LogMinerDmlParser will report an IndexOutOfBoundsException when the following steps are performed:

      1. Create any table in a tablespace available to the connector.
      2. Add the created table to the include lists & restart connector.
      3. Issue ALTER against the table to add a new column.
      4. Issue INSERT into this new table.

      Assuming table had 4 columns and a 5th was added, should result in a IOBE:

      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)
      

      Attachments

        Issue Links

          Activity

            People

              ccranfor@redhat.com Chris Cranford
              ccranfor@redhat.com Chris Cranford
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: