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

Support keyword CHAR SET for defining charset options

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 1.8.0.CR1
    • 1.7.1.Final
    • mysql-connector
    • None

      mysql version 5.7.29

      kafka-connect 2.8.1

       

      io.debezium.DebeziumException: Error processing binlog event
      at io.debezium.connector.mysql.MySqlStreamingChangeEventSource.handleEvent(MySqlStreamingChangeEventSource.java:366)
      at io.debezium.connector.mysql.MySqlStreamingChangeEventSource.lambda$execute$25(MySqlStreamingChangeEventSource.java:855)
      at com.github.shyiko.mysql.binlog.BinaryLogClient.notifyEventListeners(BinaryLogClient.java:1125)
      at com.github.shyiko.mysql.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:973)
      at com.github.shyiko.mysql.binlog.BinaryLogClient.connect(BinaryLogClient.java:599)
      at com.github.shyiko.mysql.binlog.BinaryLogClient$7.run(BinaryLogClient.java:857)
      at java.lang.Thread.run(Thread.java:745)
      Caused by: io.debezium.text.ParsingException: DDL statement couldn't be parsed. Please open a Jira issue with the statement 'CREATE TABLE `daily_intelligences`(
      `id` bigint(20) NOT NULL AUTO_INCREMENT COMMENT '',
      `partner_code` varchar(32) DEFAULT NULL COMMENT '',
      `text` LONGTEXT DEFAULT NULL COMMENT '',
      `monitor_time` TIMESTAMP DEFAULT NULL COMMENT '',
      `gmt_modify` TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP COMMENT '',
      `gmt_create` TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT '',
      PRIMARY KEY (`id`)
      ) ENGINE=innodb DEFAULT CHAR SET=utf8 COMMENT '''
      no viable alternative at input 'CREATE TABLE `daily_intelligences`(\n\t`id` bigint(20) NOT NULL AUTO_INCREMENT COMMENT 'id',\n\t`partner_code` varchar(32) DEFAULT NULL COMMENT '',\n\t`text` LONGTEXT DEFAULT NULL COMMENT '',\n\t`monitor_time` TIMESTAMP DEFAULT NULL COMMENT '',\n\t`gmt_modify` TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP COMMENT '',\n `gmt_create` TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT '',\n \tPRIMARY KEY (`id`)\n) ENGINE=innodb DEFAULT CHAR'
      at io.debezium.antlr.ParsingErrorListener.syntaxError(ParsingErrorListener.java:43)

              anmohant Anisha Mohanty
              funkye 健斌 陈 (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: