Currently, if a user pairs the ExtractNewRecordState with a Debezium source record or if the input is from a non-Debezium source, users may not always want the default mapping to translate a dot in the topic name to an underscore, particularly if the transformation chain is used to prepare the topic name as schema.table.

To handle this likely everyday use case, we should introduce a special collection naming strategy, e.g. PassthroughCollectionNamingStrategy, that a user could specify in their configuration that would take the topic name, as is, and treat it as if it's the fully qualified table name in the target system.