-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
关于 canal.instance.filter.regex 设置的问题 #922
Comments
我想在表达 下我的问题: |
有参数可以关闭, 过滤掉空事务的头和尾 |
在canal.properteis 里面只有一个是true 其他全部可以改为false canal.instance.filter.query.dcl = true 这个配置就是把默认产生的sql语句给过滤掉,也就是binlog日志改为row模式后,还是会有一条EntryType为QUERY的sql语句 |
您好,有点不是很明白,只有一个可以为true,其他全可以改为false的意思。他默认本身就全是false。我怎么改都不能获取正常的eventype。全是事务的eventype |
版本 1.0.24
@agapple
问题现象:
在同一个mysql中
我的canal.instance.filter.regex=cms\.rc_.*,意思是只订阅cms数据库下的rc_开头的表,这样是没问题的。
但是我在debug代码时,我修改其它数据库下的表 比如 我修改 test数据库下的表,我的客户端还是能接收到消息,消息的 entryType 只有TRANSACTIONBEGIN和TRANSACTIONEND;虽然这两个消息并不是我想要的,但是我还是希望不要收到其它数据库修改后的“垃圾”消息: 垃圾消息如下:
header {
version: 1
logfileName: "mysql-bin.000001"
logfileOffset: 6882
serverId: 1
serverenCode: "UTF-8"
executeTime: 1536320325000
sourceType: MYSQL
schemaName: ""
tableName: ""
eventLength: 75
}
entryType: TRANSACTIONBEGIN
storeValue: " \036"
The text was updated successfully, but these errors were encountered: