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

DDL with Oracle SDO_GEOMETRY cannot be parsed

XMLWordPrintable

    • False
    • False
    • Hide
      1. Create a table with SDO_GEOMETRY column (see the SQL attached)
      2. Start Kafka Connect with Debezium Oracle connector installed
      3. Configure Debezium Oracle connector to watch the table from step 1
      4. Insert a record into the table (see the SQL attached)
        ==> Connector's task fails (see the log attached)
      Show
      Create a table with SDO_GEOMETRY column (see the SQL attached) Start Kafka Connect with Debezium Oracle connector installed Configure Debezium Oracle connector to watch the table from step 1 Insert a record into the table (see the SQL attached) ==> Connector's task fails (see the log attached)

      Debezium 1.7.0 DDL parser not able to parse "create table" DDL with Oracle 19c SDO_GEOMETRY column. Below is the error logged:

      ...
      kafka-connect      | io.debezium.text.ParsingException: DDL statement couldn't be parsed. Please open a Jira issue with the statement '
      kafka-connect      |   CREATE TABLE "PRISM_JOB"."JOB" 
      kafka-connect      |    (       "ID" NUMBER(19,0) NOT NULL ENABLE, 
      kafka-connect      |    "NAME" VARCHAR2(100) NOT NULL ENABLE, 
      kafka-connect      |    "LOCATION" "SDO_GEOMETRY"
      kafka-connect      |    ) 
      kafka-connect      |  VARRAY "LOCATION"."SDO_ELEM_INFO" STORE AS SECUREFILE LOB 
      kafka-connect      |  VARRAY "LOCATION"."SDO_ORDINATES" STORE AS SECUREFILE LOB ;'
      kafka-connect      | extraneous input 'AS' expecting {<EOF>, 'ABORT', 'ABS', 'ACCESS', 'ACCESSED', 'ACCOUNT', 'ACL', 'ACOS', 'ACTION', 'ACTIONS', 'ACTIVATE', 'ACTIVE', 'ACTIVE_COMPONENT', 'ACTIVE_DATA', 'ACTIVE_
      ....
      

      Full logged attached.

              ccranfor@redhat.com Chris Cranford
              stsymbal Sergii Tsymbal (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: