Feature request or enhancement

For feature requests or enhancements, provide this information, please:

Which use case/requirement will be addressed by the proposed feature?

In DBZ-6775 to handle schema changes per shard, we now have the shard as the catalog. This means that for users that specified a DefaultTopicNamingStrategy now the shard will be included in the topic (since now catalog is no longer null). This topic naming strategy before the changes to set catalog to shard, was basically just a table only topic naming strategy. So we should add a topic naming strategy in order for users to be able to preserve their topic.prefix key (which is used to store state) and give them the same resulting topic names (which are just the table, which is added to the prefix).

If users need to change their topic.prefix then this causes issues with stored state. If users do not change their topic naming strategy then their connectors may fail due to outputting to non-existent topics or if auto topic creation is on then they would create topics for every shard. By adding this new topic naming strategy, both of these issues can be avoided and the behavior after the upgrade will be the same.

Implementation ideas (optional)

See previous section