coco created FLINK-25264:
----------------------------
Summary: Does the binlog_row_image of MySQL must be in full mode
when Flink CDC is used?
Key: FLINK-25264
URL: https://issues.apache.org/jira/browse/FLINK-25264
Project: Flink
Issue Type: Bug
Components: Table SQL / API
Affects Versions: 1.13.3
Reporter: coco
Fix For: 1.13.3
When I use Flink CDC to connect to MySQL, I encounter the following problems:
Connection gracefully closed
Uncaught exception in the SplitEnumerator for Source Source:
TableSourceScan(table=[[default_catalog, default_database,
t_alarm_op_record_202112]], fields=[CSN, OPERATION, OPERATOR, UTCTIME,
CONTENT]) while starting the SplitEnumerator.. Triggering job failover.
org.apache.flink.table.api.ValidationException: {color:#FF0000}*The MySQL
server is configured with binlog_row_image MINIMAL rather than FULL, which is
required for this connector to work properly. Change the MySQL configuration to
use a binlog_row_image=FULL and restart the connector.*{color}
at
com.ververica.cdc.connectors.mysql.MySqlValidator.checkBinlogRowImage(MySqlValidator.java:132)
~[flink-connector-mysql-cdc-2.0.0.jar:2.0.0]
...
Check the MySQL configuration.
Mysql> select @@global.binlog_row_image,@@session.binlog_row_image;
It is indeed MINIMAL.
Does the binlog_row_image of MySQL must be in full mode when Flink CDC is used?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
