[
https://issues.apache.org/jira/browse/KAFKA-7775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749226#comment-16749226
]
Matthias J. Sax commented on KAFKA-7775:
----------------------------------------
Thanks for reporting this. It's a know issue, however not easy to resolve.
We need to use "topic." and "admin." prefix to pass-though configs via
`ConsumerConfig` to use them within `InternalTopicManager` or feed those
configs into `AdminClient`.
I think a proper fix would change `AbstractConfig` and add a new "pass through"
config capability. The idea would be, to specify a prefix (like "passthrough.")
that can be added to any config. For all those configs, no WARN would be
logged, and while forwarding those config the prefix would be removed. This
would be public API change and requires a KIP though (cf
[https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals])
> [KStream] remove topic prefix from consumer configuration to resolve
> unnecessary warning
> ----------------------------------------------------------------------------------------
>
> Key: KAFKA-7775
> URL: https://issues.apache.org/jira/browse/KAFKA-7775
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Affects Versions: 2.1.0
> Reporter: Ludo
> Priority: Minor
> Labels: needs-kip, newbie++
>
> When using topic configuration, every stream startup when using
> configurations :
> {noformat}
> topic.{noformat}
> or method :
> {noformat}
> public static String topicPrefix(final String topicProp){noformat}
> Will emit this warning :
>
> {code:java}
> log.warn("The configuration '{}' was supplied but isn't a known config.",
> key);
> {code}
> This fix will remove the warning
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
