You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Rens Groothuijsen (JIRA)" <ji...@apache.org> on 2019/05/26 12:18:00 UTC

[jira] [Commented] (KAFKA-2939) Make AbstractConfig.logUnused() tunable for clients

    [ https://issues.apache.org/jira/browse/KAFKA-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16848414#comment-16848414 ] 

Rens Groothuijsen commented on KAFKA-2939:
------------------------------------------

Took a shot at implementing the boolean idea, though this would mean the 3 places where logUnused() is actually called (KafkaConsumer, KafkaProducer and KafkaAdminClient) would also need to have an extra boolean tacked on to their constructors. It looks very hacky, to be honest.

> Make AbstractConfig.logUnused() tunable for clients
> ---------------------------------------------------
>
>                 Key: KAFKA-2939
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2939
>             Project: Kafka
>          Issue Type: Improvement
>          Components: config
>            Reporter: Guozhang Wang
>            Assignee: Rens Groothuijsen
>            Priority: Major
>              Labels: newbie
>
> Today we always log unused configs in KafkaProducer / KafkaConsumer in their constructors, however for some cases like Kafka Streams that make use of these clients, other configs may be passed in to configure Partitioner / Serializer classes, etc. So it would be better to make this function call optional to avoid printing unnecessary and confusing WARN entries.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)