-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
None
-
None
-
None
History records were filtered by white/black list before storing to kafka db history topic, which will cause some debezium connector config modification not to take effect.
As we know, kafka connect will restart debezium connector when it detected config modification, and debezium will restore `tables` from db history topic.
Then we will found the extended table white list didn't take effect, since the related table meta was filtered before.
Can you help resolve it?
- duplicates
-
DBZ-175 table.whitelist option update for an existing connector doesn't work
- Closed