KelvinChi opened a new issue, #6870: URL: https://github.com/apache/seatunnel/issues/6870
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22bug%22) and found no similar issues. ### What happened I am using OGG to write change data of two tables into the same Kafka Topic. By configuring ogg_json.table.include in the configuration file, I cannot achieve seatunnel to consume the corresponding tables in Kafka, and there will be errors reporting that the primary key cannot be null. ### SeaTunnel Version 2.3.5 ### SeaTunnel Config ```conf env { parallelism = 2 job.mode = "streaming" checkpoint.interval = 3000 } source { Kafka { bootstrap.servers = "xx.xx.xx.xx:9092,xx.xx.xx.xx:9092,xx.xx.xx.xx:9092" topic = "xx_topic" consumer.group = "xx_scandata" format = ogg_json ogg_json.database.include = "XX_XXXX" ogg_json.table.include = "SCANDATA" schema = { fields { TE_IMES07_SCANDATA_ID = "BIGINT" ORDER_NO = "STRING" VIN = "STRING" MATERIAL_NO = "STRING" PLANT_NO = "STRING" TPS = "STRING" ULOC_ID = "STRING" QUAN = "DECIMAL(38, 18)" SCAN_TIME = "DATE" } } } } sink { StarRocks { base-url = "jdbc:mysql://xx.xx.xx.xx:9030" nodeUrls = ["xx.xx.xx.xx:8030", "xx.xx.xx.xx:8030", "xx.xx.xx.xx:8030"] username = "root" password = "xxxxxxxx" database = "test" table = "SCANDATA" enable_upsert_delete = true } } ``` ### Running Command ```shell bin/seatunnel.sh -c scandata_streaming.config ``` ### Error Exception ```log logs/seatunnel-engine-server.log.2024-05-17-1:Error: NULL value in non-nullable column 'TE_IMES07_SCANDATA_ID'. Row: [NULL, NULL, NULL, 'S0BEFCL6F200400338', '5001', NULL, NULL, NULL, NULL] ``` ### Zeta or Flink or Spark Version Zeta ### Java or Scala Version Java ### Screenshots _No response_ ### Are you willing to submit PR? - [X] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
