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

Check constraint introduces a column based on constraint in the schema change event.


    • False
    • None
    • False

      Bug report

      oracle ddl parser process constraint as conlumn

      using oracle-connector (logminer):

      when process a DDL like

      create table "t_ddl_0027"(
      "PID" int,
      "FID" int,
      "NAME" varchar(50) default 'Tom',
      "ADDRESS" varchar(50) not null,
      "DEPT" varchar(50),
      constraint "PK_ID" primary key("PID"),
      constraint "CK_DEPT" check("DEPT" in('IT','sales','manager'))



      debezium process  constraint "CK_DEPT" check("DEPT" in('IT','sales','manager')) as a column 

      so the data in Table will have wrong column

      when this table have change data. debezium will send message to kafka . and the message in before/after will have wrong field.

      What Debezium connector do you use and what version?


      What is the connector configuration?

      <Your answer>

      What is the captured database version and mode of depoyment?


      What behaviour do you expect?

       when parser column check 'CHECK' property 



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



            anmohant Anisha Mohanty
            saximoer sheng pu (Inactive)
            0 Vote for this issue
            6 Start watching this issue