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

Datatype mdsys.sdo_geometry not supported


    • False
    • None
    • False

      In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

      Bug report

      As you can see, DDL statement couldn't be parsed.The ddl like this:

      CREATE TABLE test9 (
      doc mdsys.sdo_geometry

      But if the ddl like this,it can be  parsed.

      CREATE TABLE test7 (
      doc "SYS"."SDO_GEOMETRY"

      I know,the sdo_geometry is not supported by debezium.But I think the DDL statement about sdo_geometry should can be parsed.I have seen the code to parse sdo_geometry in debezium 1.8.1 final . If there have the schema of datatype  like sys.xmltype, mdsys.sdo_geometry,the debezium may not be parsed.I want to know 
      whether there have some solutions to parse mdsys.geometry.Should I add somethings to the Parser.g4 or Lexer.g4?

      What Debezium connector do you use and what version?

      debezium-connector-oracle 1.8.1 finally 

      What is the connector configuration?

          "name": "oracle-test",

      {             "connector.class": "io.debezium.connector.oracle.OracleConnector",             "database.server.name": "CDC",             "database.hostname": "******",             "database.port": "1521",             "database.user": "C##DBZUSER",             "database.password": "*****",             "database.dbname": "CDB19C",             "database.pdb.name": "PDB1",             "schema.include.list": "debezium",             "offset.storage": "org.apache.kafka.connect.storage.FileOffsetBackingStore",             "lob.enabled":"true",             "offset.flush.interval.ms": "6000",             "database.connection.adapter": "xstream",             "database.out.server.name" : "dbzxout",             "database.history.kafka.bootstrap.servers": "",             "database.history.kafka.topic": "oracle.history",             "key.converter.schemas.enable": "true",             "value.converter.schemas.enable": "true",             "snapshot.mode": "schema_only",             "provide.transaction.metadata": "true",             "transforms": "route",             "transforms.route.type": "org.apache.kafka.connect.transforms.RegexRouter",             "transforms.route.regex":"([^.]+)\\.([^.]+)\\.([^.]+)$",             "transforms.route.replacement":"$1.$2.ALL_TABLES",             "snapshot.locking.mode":"none"     }


      What is the captured database version and mode of depoyment?

      (E.g. on-premises, with a specific cloud provider, etc.)

      <Your answer>

      oracle 19.3.0 single node 

      What behaviour do you expect?

      <Your answer>

      What behaviour do you see?

      <Your answer>

      Do you see the same behaviour using the latest relesead Debezium version?

      (Ideally, also verify with latest Alpha/Beta/CR version)

      <Your answer>

      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>

            Unassigned Unassigned
            rusignalflag SignalFlag Ru (Inactive)
            0 Vote for this issue
            5 Start watching this issue