如何将canal的MySQL select权限粒度细化到更细的级别？

今天产品问了一个问题，问懵了 产品：canal在开通mysql权限时需要哪些权限 我：SELECT, REPLICATION SLAVE, REPLICATION CLIENT 产品：那SELECT权限要开通到表级还是库级（我们使用canal同步数据时最终选择到表） 我：en..... 晚会给你答案吧^-^. 于是乎今天就测试一下，不测不知道，一测怎加不加select权限都能正常同步binlog 场景一 本地有个mysql，直接在本地测试，删除库的select权限，也能正常同步binlog，于是乎就不淡定了，在网上查也没有个所以然 场景二 于是启动本地基于mha搭建的mysql高可用集群，再来使用canal同步主库binlog，将所要同步库的select权限删除，发现报错： 16:07:42.791 [WARN ] [destination = example7 , address = s129/192.168.3.129:3306 , EventParser] MysqlEventParser:463 | ERROR ## parse this event has an error , last position : [EntryPosition[included=false,journalName=mysql-bin.000009,position=4667,serverId=1,gtid=,timestamp=1615016220000]] com.alibaba.otter.canal.parse.exception.CanalParseException: parse row data failed. Caused by: com.alibaba.otter.canal.parse.exception.CanalParseException: com.google.common.util.concurrent.UncheckedExecutionException: com.alibaba.otter.canal.parse.exception.CanalParseException: fetch failed by table meta:`canal`.`test_canal_2_hive` Caused by: com.google.common.util.concurrent.UncheckedExecutionException: com.alibaba.otter.canal.parse.exception.CanalParseException: fetch failed by table meta:`canal`.`test_canal_2_hive` at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2203) ~[guava-18.0.jar:na] at com.google.common.cache.LocalCache.get(LocalCache.java:3937) ~[guava-18.0.jar:na] at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3941) ~[guava-18.0.jar:na] at com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:4824) ~[guava-18.0.jar:na] at com.google.common.cache.LocalCache$LocalLoadingCache.getUnchecked(LocalCache.java:4830) ~[guava-18.0.jar:na] at com.alibaba.otter.canal.parse.inbound.mysql.dbsync.TableMetaCache.getTableMeta(TableMetaCache.java:195) ~[canal.parse-1.1.4.jar:na] at com.alibaba.otter.canal.parse.inbound.mysql.dbsync.LogEventConvert.getTableMeta(LogEventConvert.java:950) ~[canal.parse-1.1.4.jar:na] at com.alibaba.otter.canal.parse.inbound