开发者社区> 问答> 正文

删除索引时出现了NullPointerException异常

canal-server version:1.1.5 exceptinInfo : 2022-04-13 10:53:03.395 [MultiStageCoprocessor-other-ydcloud-0] WARN c.a.otter.canal.parse.inbound.mysql.tsdb.MemoryTableMeta - parse faield : DROP INDEX uk_code ON D3B25DAE0AC045D5BCB3D1A47B3847CB.official_swb_salary_item_config java.lang.NullPointerException: null at com.alibaba.druid.sql.ast.statement.SQLCreateTableStatement.apply(SQLCreateTableStatement.java:844) ~[druid-1.2.6.jar:1.2.6] at com.alibaba.druid.sql.repository.SchemaRepository.acceptDropIndex(SchemaRepository.java:982) ~[druid-1.2.6.jar:1.2.6] at com.alibaba.druid.sql.repository.SchemaRepository$MySqlConsoleSchemaVisitor.visit(SchemaRepository.java:681) ~[druid-1.2.6.jar:1.2.6] at com.alibaba.druid.sql.ast.statement.SQLDropIndexStatement.accept0(SQLDropIndexStatement.java:86) ~[druid-1.2.6.jar:1.2.6] at com.alibaba.druid.sql.ast.SQLObjectImpl.accept(SQLObjectImpl.java:49) ~[druid-1.2.6.jar:1.2.6] at com.alibaba.druid.sql.repository.SchemaRepository.console(SchemaRepository.java:503) ~[druid-1.2.6.jar:1.2.6] at com.alibaba.otter.canal.parse.inbound.mysql.tsdb.MemoryTableMeta.apply(MemoryTableMeta.java:84) ~[canal.parse-1.1.5.jar:na] at com.alibaba.otter.canal.parse.inbound.mysql.tsdb.DatabaseTableMeta.apply(DatabaseTableMeta.java:147) [canal.parse-1.1.5.jar:na] at com.alibaba.otter.canal.parse.inbound.mysql.dbsync.TableMetaCache.apply(TableMetaCache.java:238) [canal.parse-1.1.5.jar:na] at com.alibaba.otter.canal.parse.inbound.mysql.dbsync.LogEventConvert.parseQueryEvent(LogEventConvert.java:292) [canal.parse-1.1.5.jar:na] at com.alibaba.otter.canal.parse.inbound.mysql.dbsync.LogEventConvert.parse(LogEventConvert.java:120) [canal.parse-1.1.5.jar:na] at com.alibaba.otter.canal.parse.inbound.mysql.MysqlMultiStageCoprocessor$SimpleParserStage.onEvent(MysqlMultiStageCoprocessor.java:303) [canal.parse-1.1.5.jar:na] at com.alibaba.otter.canal.parse.inbound.mysql.MysqlMultiStageCoprocessor$SimpleParserStage.onEvent(MysqlMultiStageCoprocessor.java:251) [canal.parse-1.1.5.jar:na] at com.lmax.disruptor.BatchEventProcessor.processEvents(BatchEventProcessor.java:168) [disruptor-3.4.2.jar:na] at com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:125) [disruptor-3.4.2.jar:na] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_292] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_292] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_292] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_292] at java.lang.Thread.run(Thread.java:748) [na:1.8.0_292]

原提问者GitHub用户helei810304

展开
收起
后端老大 2023-04-26 15:45:52 87 0
1 条回答
写回答
取消 提交回答
  • 这条SQL我测试了1.1.6版本没问题,可以考虑升级下

    原回答者GitHub用户agapple

    2023-04-26 18:39:46
    赞同 展开评论 打赏
问答地址:
问答排行榜
最热
最新

相关电子书

更多
低代码开发师(初级)实战教程 立即下载
冬季实战营第三期:MySQL数据库进阶实战 立即下载
阿里巴巴DevOps 最佳实践手册 立即下载