[FLINK-25264] Does the binlog_row_image of MySQL must be in full mode when Flink CDC is used?

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Invalid
• Affects Version/s: 1.13.3
• Fix Version/s: 1.13.3
• Component/s: Table SQL / API
• Labels: Flink-CDC MySQL
• Flags: Important
• Assignee: Unassigned
• Reporter: coco
• Created: 12/Dec/21 11:58
• Updated: 13/Dec/21 17:05
• Resolved: 13/Dec/21 17:05

Description

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: 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.
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?