[
https://issues.apache.org/jira/browse/KAFKA-13497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479034#comment-17479034
]
Spencer Carlson commented on KAFKA-13497:
-----------------------------------------
My request is very similar to what is already being done in
[Cast.java#L170|[https://github.com/apache/kafka/blob/99b9b3e84f4e98c3f07714e1de6a139a004cbc5b/connect/transforms/src/main/java/org/apache/kafka/connect/transforms/Cast.java#L170].]
It seems preferable to be able to enable trace or debug logging and see with
certainty that the topic is being transformed how I expect, then to have to
look at the source code, reverse engineer how the callbacks fire to set
`replacement`, and then recreate the same snippet of java code.
> Debug Log RegexRouter transform
> -------------------------------
>
> Key: KAFKA-13497
> URL: https://issues.apache.org/jira/browse/KAFKA-13497
> Project: Kafka
> Issue Type: Improvement
> Components: KafkaConnect
> Reporter: Spencer Carlson
> Priority: Minor
>
> It is hard to troubleshoot regex transformations without knowing exactly what
> the new topic transformation is.
>
> Can we add a debug log in the
> [RegexRouter.java#L59|https://github.com/apache/kafka/blob/99b9b3e84f4e98c3f07714e1de6a139a004cbc5b/connect/transforms/src/main/java/org/apache/kafka/connect/transforms/RegexRouter.java#L59]
> to print out the transformed topic
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
