-
Enhancement
-
Resolution: Unresolved
-
Major
-
None
-
None
-
False
-
None
-
False
-
-
As a follow-up to DBZ-5423, if a user performs a rename on a table and creates a new change table instance, currently the user is required to restart the connector so that the connector refreshes the change table pointer cache.
As a way to avoid the connector restart, we could consider adding a new signal that could be sent to the connector that would in essence do a restart of the streaming phase but not the entire connector, allowing the change table pointer cache to be refreshed.
- relates to
-
DBZ-5423 SQL table rename affect on Kafka connector and topic
- Closed