问题描述
在将新表列入debezium mysql连接器的白名单中,是否遵循最佳实践?
Are there any best practices that are followed for whitelisting a new table to the debezium mysql connector ?
我们在CDC流程中使用了debezium mysql连接器,并且出现了一个用例,将更多表列入连接器配置白名单.以下是所使用的debezium和
We are using debezium mysql connector for our CDC flows and a use case has arised to whitelist more tables to the connector configuration. Here are the version details of the debezium being used and the
{
"class": "io.debezium.connector.mysql.MySqlConnector",
"version": "0.8.0.Final",
"snapshot.mode": "schema_only"
}
有一个debezium票证 https://issues.redhat.com/browse/DBZ-906 表示要在
There is a debezium ticket https://issues.redhat.com/browse/DBZ-906 which indicates to run the connector in
"snapshot.mode": "schema_only_recover"
模式,并在重新启动连接器之前重新创建历史记录主题.关于这种方法,我有几个问题
mode and to recreate the history topic before restarting the connector. I had a couple of questions regarding this approach
推荐答案
首先,请eupgrade Debezium,因为0.8.0版本非常老.
first of all, pleas eupgrade Debezium as version 0.8.0 is very old.
通常,有多种方法可以解决您的问题,但是如果您可以在流媒体中暂停一下,那么我建议您1)停止当前的连接器2)使用列入白名单的新表启动新连接器以在其上执行快照3)快照完成后,使用更新的白名单表列表启动原始连接器
Generally there are multiple approaches to solving your issue but if you can afford a pause in streaming than I'd recommend to1) Stop the current connector2) Start a new connector with whitelisted new table to execute the snapshot on it3) When snapshot is completed then start the original connector with updated whitelist table list
如果您无法承担停机时间,请检查 DBZ-175 中引入的实验方法.a>
If you cannot afford the downtime then please check the experimental approach introduced in DBZ-175
这篇关于在Debezium Mysql Connector中将更多表列入白名单的有效方法的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!