Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

启动deployer日志中出现druid解析sql错误信息 #4899

Open
Dkbei opened this issue Oct 8, 2023 · 8 comments
Open

启动deployer日志中出现druid解析sql错误信息 #4899

Dkbei opened this issue Oct 8, 2023 · 8 comments

Comments

@Dkbei
Copy link

Dkbei commented Oct 8, 2023

com.alibaba.druid.sql.parser.ParserException: illegal name, pos 24488, line 623, column 3, token TO
at com.alibaba.druid.sql.parser.SQLExprParser.name(SQLExprParser.java:2370)
at com.alibaba.druid.sql.dialect.mysql.parser.MySqlExprParser.parseColumn(MySqlExprParser.java:981)
at com.alibaba.druid.sql.dialect.mysql.parser.MySqlCreateTableParser.parseCreateTable(MySqlCreateTableParser.java:435)
at com.alibaba.druid.sql.dialect.mysql.parser.MySqlStatementParser.parseCreate(MySqlStatementParser.java:296)
at com.alibaba.druid.sql.parser.SQLStatementParser.parseStatementList(SQLStatementParser.java:245)
at com.alibaba.druid.sql.SQLUtils.parseStatements(SQLUtils.java:599)
at com.alibaba.druid.sql.repository.SchemaRepository.console(SchemaRepository.java:468)
at com.alibaba.otter.canal.parse.inbound.mysql.tsdb.MemoryTableMeta.apply(MemoryTableMeta.java:85)
at com.alibaba.otter.canal.parse.inbound.mysql.tsdb.DatabaseTableMeta.buildMemFromSnapshot(DatabaseTableMeta.java:423)
at com.alibaba.otter.canal.parse.inbound.mysql.tsdb.DatabaseTableMeta.rollback(DatabaseTableMeta.java:166)
at com.alibaba.otter.canal.parse.inbound.mysql.AbstractMysqlEventParser.processTableMeta(AbstractMysqlEventParser.java:142)
at com.alibaba.otter.canal.parse.inbound.AbstractEventParser$1.run(AbstractEventParser.java:192)
at java.lang.Thread.run(Thread.java:748)
2023-10-07 19:11:44.925 [destination = xx.xx.xx.xx, address = /xx.xx.xx.xx:3306 , EventParser] WARN c.a.o.c.p.inbound.mysql.rds.RdsBinlogEventParserProxy - ---> find start position successfully, EntryPosition[included=false,journalName=mysql-bin.000094,position=63919272,serverId=1,gtid=,timestamp=1696677103000] cost : 64ms , the next step is binlog dump

canal版本:canal-1.1.7-alpha-3
mysql版本: 5.6.41
deployer启动后好像需要通过druid解析一些建表sql,导致waraing info出现,异常出现时不影响数据同步

@Dkbei
Copy link
Author

Dkbei commented Oct 8, 2023

希望大佬能看到,并进行回复,如果解决这种问题呢?

@agapple
Copy link
Member

agapple commented Oct 9, 2023

具体报错的日志没发出来啊,SQL解析报错的语句是啥

@Dkbei
Copy link
Author

Dkbei commented Oct 9, 2023

具体报错的日志没发出来啊,SQL解析报错的语句是啥
sql_parse.log
大佬,日志中提示有多段错误,您看看

@Dkbei
Copy link
Author

Dkbei commented Oct 9, 2023

具体报错的日志没发出来啊,SQL解析报错的语句是啥
还有个问题大佬,版本canal-1.1.7-alpha-3,启动deployer后没有打开11112端口,不知道是不是bug,日志中没有任何相关的错误

@Dkbei
Copy link
Author

Dkbei commented Oct 9, 2023

具体报错的日志没发出来啊,SQL解析报错的语句是啥
还有个问题大佬,版本canal-1.1.7-alpha-3,启动deployer后没有打开11112端口,不知道是不是bug,日志中没有任何相关的错误

测试了,1.1.5 版本启动后正常打开了11112端口的

@Hisioni
Copy link

Hisioni commented Oct 21, 2023

一样的错误,这样的日志真的没法调试...

@Licheng-Xu
Copy link

Licheng-Xu commented Nov 21, 2023

具体报错的日志没发出来啊,SQL解析报错的语句是啥
sql_parse.log
大佬,日志中提示有多段错误,您看看

com.alibaba.druid.sql.parser.ParserException: illegal name, pos 24488, line 623, column 3, token TO

看起来 oozie_email 这个表的 to 字段名是 MySQL 保留字,druid sql 解析失败

@agapple
Copy link
Member

agapple commented Jan 15, 2024

建表语句有关键字,这个应该是TableMetaTSDB输出时未做转义导致,最新主干增加了转义输出的处理,避免节点重启或者重置位点时DDL解析失败

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants