canal Value too long for column "CHARACTER VARYING"

gupuwyp2  于 22天前  发布在  其他
关注(0)|答案(3)|浏览(18)
  • I have searched the issues of this repository and believe that this is not a duplicate.
  • I have checked the FAQ of this repository and believe that this is not a duplicate.

environment

ubuntu20

  • canal version
  • 1.1.8-alpha
  • mysql version
    mysql Ver 14.14 Distrib 5.7.42, for Linux (x86_64) using EditLine wrapper

Issue Description

2024-03-30 20:17:20.511 [main] INFO c.a.otter.canal.instance.core.AbstractCanalInstance - start successful....
2024-03-30 20:17:20.512 [destination = example , address = /127.0.0.1:3306 , EventParser] WARN c.a.o.c.p.inbound.mysql.rds.RdsBinlogEventParserProxy - prepare to find start position just show master status
2024-03-30 20:17:20.517 [destination = example , address = /127.0.0.1:3306 , EventParser] WARN c.a.otter.canal.parse.inbound.mysql.MysqlConnection - load MySQL @@version_comment : MySQL Community Server (GPL)
2024-03-30 20:17:22.855 [destination = example , address = /127.0.0.1:3306 , EventParser] ERROR c.a.o.c.p.inbound.mysql.rds.RdsBinlogEventParserProxy - dump address /127.0.0.1:3306 has an error, retrying. caused by
com.alibaba.otter.canal.parse.exception.CanalParseException: apply failed caused by : nested exception is org.apache.ibatis.type.TypeException: Could not set parameters for mapping: ParameterMapping{property='data', mode=IN, javaType=class java.lang.String, jdbcType=null, numericScale=null, resultMapId='null', jdbcTypeName='null', expression='null'}. Cause: org.apache.ibatis.type.TypeException: Error setting non null for parameter #6 with JdbcType null . Try setting a different JdbcType for this parameter or a different configuration property. Cause: org.h2.jdbc.JdbcSQLDataException: Value too long for column "CHARACTER VARYING": "{"" dev_aiguo_renew "":""CREATE TABLE a_ jindu_monitor_log (\n\t jindu_monitor_lo... (1407702)" [22001-210] Caused by: org.mybatis.spring.MyBatisSystemException: nested exception is org.apache.ibatis.type.TypeException: Could not set parameters for mapping: ParameterMapping{property='data', mode=IN, javaType=class java.lang.String, jdbcType=null, numericScale=null, resultMapId='null', jdbcTypeName='null', expression='null'}. Cause: org.apache.ibatis.type.TypeException: Error setting non null for parameter #6 with JdbcType null . Try setting a different JdbcType for this parameter or a different configuration property. Cause: org.h2.jdbc.JdbcSQLDataException: Value too long for column "CHARACTER VARYING": "{"" dev_aiguo_renew "":""CREATE TABLE a_ jindu_monitor_log (\\n\\t jindu_monitor_lo... (1407702)" [22001-210]
at org.mybatis.spring.MyBatisExceptionTranslator.translateExceptionIfPossible(MyBatisExceptionTranslator.java:92)
at org.mybatis.spring.SqlSessionTemplate$SqlSessionInterceptor.invoke(SqlSessionTemplate.java:440)
at com.sun.proxy.$Proxy10.insert(Unknown Source)
at org.mybatis.spring.SqlSessionTemplate.insert(SqlSessionTemplate.java:271)
at org.apache.ibatis.binding.MapperMethod.execute(MapperMethod.java:62)
at org.apache.ibatis.binding.MapperProxy$PlainMethodInvoker.invoke(MapperProxy.java:152)
at org.apache.ibatis.binding.MapperProxy.invoke(MapperProxy.java:85)
at com.sun.proxy.$Proxy11.insert(Unknown Source)
at com.alibaba.otter.canal.parse.inbound.mysql.tsdb.dao.MetaSnapshotDAO.insert(MetaSnapshotDAO.java:17)
at com.alibaba.otter.canal.parse.inbound.mysql.tsdb.DatabaseTableMeta.applySnapshotToDB(DatabaseTableMeta.java:345)
at com.alibaba.otter.canal.parse.inbound.mysql.tsdb.DatabaseTableMeta.rollback(DatabaseTableMeta.java:176)
at com.alibaba.otter.canal.parse.inbound.mysql.AbstractMysqlEventParser.processTableMeta(AbstractMysqlEventParser.java:145)
at com.alibaba.otter.canal.parse.inbound.AbstractEventParser$1.run(AbstractEventParser.java:192)
at java.lang.Thread.run(Thread.java:750)
我试了1.1.8和1.1.7相同的错误
1.1.6运行正常

Steps to reproduce

Expected behaviour

Actual behaviour

If there is an exception, please attach the exception trace:

Just put your stack trace here!
xbp102n0

xbp102n01#

遇见相同的问题,升级h2的jar,使用2.2.224版本替换2.1.210版本。

tag5nh1u

tag5nh1u2#

遇见相同的问题,升级h2的jar,使用2.2.224版本替换2.1.210版本。

升级jar包后解决这个问题了吗?

ldxq2e6h

ldxq2e6h3#

遇见相同的问题,升级h2的jar,使用2.2.224版本替换2.1.210版本。

升级jar包后解决这个问题了吗?

我也遇到这个问题了,升级了就可以了

相关问题