求解：解析binlog抛出异常 column size is not match for table

使用版本 canal.deployer-1.1.3-SNAPSHOT.tar.gz 异常信息： 2019-02-15 10:35:36.342 [destination = test , address = /172.17.139.231:3366 , EventParser] WARN c.a.o.c.p.inbound.mysql.rds.RdsBinlogEventParserProxy - ---> begin to find start position, it will be long time for reset or first position 2019-02-15 10:35:36.343 [destination = test , address = /172.17.139.231:3366 , EventParser] WARN c.a.o.c.p.inbound.mysql.rds.RdsBinlogEventParserProxy - prepare to find start position just last position {"identity":{"slaveId":-1,"sourceAddress":{"address":"172.17.139.231","port":3366}},"postion":{"gtid":"","included":false,"journalName":"mysql-bin.001303","position":523652,"serverId":1877583954,"timestamp":1550138420000}} 2019-02-15 10:35:36.353 [destination =test , address = /172.17.139.231:3366 , EventParser] WARN c.a.o.c.p.inbound.mysql.rds.RdsBinlogEventParserProxy - ---> find start position successfully, EntryPosition[included=false,journalName=mysql-bin.001303,position=523652,serverId=1877583954,gtid=,timestamp=1550138420000] cost : 11ms , the next step is binlog dump 2019-02-15 10:35:36.496 [destination = test , address = /172.17.139.231:3366 , EventParser] ERROR c.a.o.c.p.inbound.mysql.rds.RdsBinlogEventParserProxy - dump address 172.17.139.231/172.17.139.231:3366 has an error, retrying. caused by com.alibaba.otter.canal.parse.exception.CanalParseException: com.alibaba.otter.canal.parse.exception.CanalParseException: parse row data failed. Caused by: com.alibaba.otter.canal.parse.exception.CanalParseException: parse row data failed. Caused by: com.alibaba.otter.canal.parse.exception.CanalParseException: column size is not match for table:user.test_user,30 vs 27

biglog部分信息：

源码：

没搞懂是怎么回事？是否会影响数据同步？

原提问者GitHub用户zwh201806